fix response status assertions like:

expectError(reqSpec.then().assertThat().statusCode(is(404))).body
expectResponse(reqSpec.then().assertThat().statusCode(is(200)), Response.class)

to:

expectErrorBody(reqSpec, HttpStatus.NOT_FOUND)
expectResponse(reqSpec, HttpStatus.OK, Response.class)

1. Create

POST $BASE_URL/BOARD
-h "Authentication: Token [......]

Choose one:

1. Kotlin/JS + ReactJS
2. Flutter web

Post body
UPDATE / DELETE assertions

First 10 replies: after #28 is complete.

AS-IS

endpoint/v1/*/dto/*(Request|Response)

TO-BE

endpoint/v1/*/request/*Request
endpoint/v1/*/response/*Response

• Solve "org.jruby.exceptions.MainExitException: unknown encoding name x-windows-850" problem
• Pretty print HTML
• Link to common object types (i.e. BoardTestBase)
• Link to basic enum object types
• Find a way to separate documentation fragments
• Solve macro rendering problems

Log all user activities for administration

• Create a flutter project
• Integrate it into module app-main
• Establish development environment both API and APP
• Customise Gradle build script to deploy Flutter webApp into module app-main
• Set-up Flutter unit test environment
• Let external build script honour main build phase profile: i.e) local and release
• Final integration

Make deleting post is running via async tasks.

Refer to this documentation.

Resoliving #26 : Get first 10 replies

Integration tests and full implementations will be done at #41.

Add spec:

• rename findCurrentUser to findCurrentAccessibleUser
• getting deleted account/user's information is not allowed
• check auth/user access for deleted account

Allow READ_UNCOMMITED for non-important read operations

Consider PESSIMISTIC_LOCK for all modifying operations

• GetPostController
• ChangePasswordService
• DeleteAccountService
• RefreshAccessTokenService
• SignInService
• CloseBoardService
• CreateBoardService
• GetBoardService
• UpdateBoardService
• CreatePostService
• DeletePostService
• GetPostService
• UpdatePostService
• CreateReplyService
• DeleteReplyService
• GetRepliesService
• UpdateReplyService
• CreateUserService
• GetUserService
• UpdateUserService

ReplyRepository#findLatestByPost is no longer needed and fetch criteria must be specified by business layer, not repository layer itself.

• Remove Pageable depending logic in PageableQueryHelperMixin and its usage sites
• remove ReplyRepository#findLatestByPost call in GetRepliesServiceImpl
• cope with cases of GetRepliesService.PAGE_LATEST requests
• refactor PageableQueryHelperMixin#toFirstResultOffset to assume that requested page number is 1-based index
• refactor page number derivation logic for getting list of posts and replies
• regression test

• Default log-in name
• Default password (saved locally)
• Automatic login for certain time amounts

GET $BASE_URL/USER/loginName
-h "Authentication: Token [......]

We may refactor RepliesFetchCriteria to ContentsFetchCriteria for common usage.

• Add 'replies count' in PostBriefInfo / PostDetailedInfo
• Implement PostFetchCriteria to honour 'replies count'
• refactor PageableResponse to contain page and size information rather than offset
• Refactor PageableQueryHelperMixin to depend on type ContentFetchCriteria for offset calculation
• Task #47
• Get posts list implementation
• Apply 'replies count' in PostInfoBriefResponse
• Regression test

• Integrate project with Docker
• Acquire dynip
• Set-up NUC 4th gen hardware to host a web service

Edit history feature must be supported

PATCH $BASE_URL/TOKEN
-h "Authentication: Token [......]

{
  "refreshToken": "..."
}

Expected response upon success: same as Authentication response

DELETE $BASE_URL/BOARD/{boardId}
-h "Authentication: Token [......]

• Bump code templates
• Declare specifications and tests

Remove all paramter taking random object creation methods and implant those into TestTemplate classes.

Apply following rules under gradle

allOpen { 
    annotation("javax.persistence.Entity") 
    annotation("javax.persistence.MappedSuperclass")
    annotation("javax.persistence.Embeddable")
}

Role based or matrix based?

Actions Matrix

User

• CREATE
• UPDATE
• GET

Board

• CREATE
• UPDATE
• GET Single / List
• CLOSE
• GET Archived
• GET Closed

Post

• CREATE
• UPDATE / Edit
• UPDATE / Edit other user's
• GET Single / List
• DELETE
• DELETE other user's
• GET Archived
• GET Closed

Reply

• CREATE
• UPDATE / Edit
• UPDATE / Edit other user's
• GET Single / List
• DELETE
• DELETE other user's
• GET Archived
• GET Closed

Authorisation

• View activity
• View other user's activity

• Organise imports
• Class visibility: Hide all implementations as internal
• File comments
• Review Detekt checks
• Review Intellij checks

Since java.validation.Size is not working well for Unicode extended characters, especially for emojis, we have to create an alternative to cope those cases with.

This post might help

--- For create

• Implement request validation in Controller
• Implement integration test

--- For update

• Implement request validation in Controller
• Implement spec validation in Service
• Unit test
• Integration test

• H1 Overview
• H2 tech stacks & reason (Category/Item/Remarks)

• H1 Build & run
• H2 How to build
• H2 How to run

• H1 Measuring code quality
• H2 How to run tests
• H2 How to produce reports

• English documentation
• Spanish
• Japanese
• Korean

• Change README.md under app-main-integrationTest to AsciiDoc format

PATCH $BASE_URL/password
-h "Authentication: Token [......]

{
"newPassword": "..."
}