Website Feature List

[Afulton11]

This issue contains a feature list needed for each "page" in the website (updated often)

Key

• If a line starts with...
  • ?? = Should we add this feature?

/

• List articles with pagination, sorted by most recent
  • Up to 8 articles per page.

/signin

• Log a user in with a email and password

/signup

• Sign a user up by having them fill out the required user entity fields
• ?? email verification

/user/{username}

Provided the user exists and is NOT deleted...

• list common user information
  • ?? profile picture
• show author status vs. user status
• display graph of the user's points over time
• ?? comments for this 'user page'
  • Would require creating comment 'types' in the database
• Followers (If author)
• Following

User on their own profile

• Show the above, but with an option to edit their data
  • change email
  • Change First Name
  • Change Last Name
  • Change Birth date
  • Delete user
• Become an author
• (if author) show an articles section that summarizes all of their articles.

/article/{title}

Update Sql database article constraint Title should be unique for all articles

• display article title

• display article creation date

• display article last updated date

• display article author

• display # favorites

• display if current user has favorited

• display article category

  • ?? Allow for an article to be in up to x categories?

• display article body

• ?? Show a small "About the author" section

• Link to previous post (author's previous post by creation date)

• Link to next post (author's next post by creation date)

• Display comments on this article (with pagination)

  • Comments are fetched by simply getting all the top-level comments for an article (sorted . by creation date) and then recursively getting all the comments whose parent Id's are contained in the current list of comments.

/category/{category}

• List all articles in a category with pagination
  • shows a simple view like that shown on the home page for each article

/hiscores

?? This entire page may not be added

• list the x users with the most points currently
• list the x users with the most points since the beginning of time
• list the x users who are 'trending' (the most amount of points gained in the last 24 hours)

[fenrirmitsuki]

Okay, I believe I've written procedures for the bulk of what we need (add, update/delete, search) and organized the procedures in the file (so it's easier to browse). If you could, would you take a look at what's there and let me know what else needs to be added?

[Afulton11]

@fenrirmitsuki I noticed you have 2 have the same procedures for followers: Blog.GetFollowers and your Blog.DisplayArticle query has a GROUP BY clause, but then nothing within it.

Also, you could create a new branch named something like dev-joe or feat-sql-procedures and push to that branch instead. Then, you could create a pull request using Github to merge your branch into dev branch. This way, I could leave a review on it before you commit and make any small changes myself, or point out directly in the code what needs to be fixed before it is pushed to our developer branch.

We still need the following procedures that I could think of:

• Blog.CreateFavorite
• Blog.AddFollower
• Blog.RemoveFollower
• Blog.CreateArticleCategory
• Blog.ArchiveArticleCategory (sets the deletedAt property to the current time)
• Blog.UpdateArticleCategory (updates the name of the article)
• Blog.GetUserComments (gets all comments for a user)
• Blog.RemoveComment (given a CommentId, sets the body to null and sets DeletedAt to SYSDATETIME())

Something else I noticed too is that on many of your GET procedures you are not checking to see if the entity has already been soft deleted. For example in Blog.GetComments the where clause should be something like

WHERE Com.ArticleID = @ArticleID AND (Com.DeletedAt IS NULL OR Com.DeletedAt > SYSDATETIME())

instead of

WHERE Com.ArticleID = @ArticleID

EDIT: Sorry, comments are the 1 thing that should still exist in the return result even if it is deleted. However, almost everything else needs to be checked of is deleted.

• Also for creating a new article in your Blog.AddNewArticle you are currently requiring the CreationDateTime and LastUpdateTime to be passed in to it. These values are inserted automatically into our tables because we have those default values set. These can be removed.