Ali Sabzevari

Suggested test cases: * It should throw exception if the article does not belong to the current user. * It should call `deleteArticle` from repository. * it should throw exception...

Suggested test cases: * It should throw proper exception when article does not exist. * If the user has not been favorited the article before, the handler should not throw...

Suggested test cases: * The user should be able to only delete comment created by themselves. * It should call `deleteArticleComment` from repository.

The application uses time in different parts of the code. For example, when creating article. In order to be able to properly test handlers `Clock` should be a dependency of...

Suggested test cases: * Article slug should properly being generated from title. * It should call `insertArticle` from repository. * It should return the created article with proper initial values.

Suggested test cases: * Should throw proper exception when article not found. * If it is not a favorited article, it should call `insertFavorite` of repository. * Should throw proper...

Suggested test cases: * Should throw proper exception when article not found. * Should call `insertComment` of repository with proper values. * Should return the created comment

After upgrading to Kotlin 1.3 it is possible to use inline classes for opaque types.

model related classes are scattered everywhere in the project. They should belong to the right package and right place.

There is only one class containing all the routes and their handlers. Having separated route handlers categorized by top-level endpoint name (e.g. tags, profiles etc) makes sense.