JAMES-2884 Refresh the annotated JMAP documentation #360
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Using markdown syntax enables a better display on GitHub
LanKhuat
approved these changes
Apr 5, 2021
Arsnael
approved these changes
Apr 5, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While doing an inventory about the status of the JMAP implementation within the James server, I had the idea to review it in order to reference all JMAP related issues / partial implementation within the JIRA bugtracker. Which pointed out that I forgot many!
Of course, the doc turned out to be slightly outdated, here is my humble attempt to improve that matter of fact.
TODO: the annotated documentation should include links to the JIRA, in where we likely can better describe the issue. Who know, maybe even someone would be inspired and decide to help us fix stuff?