Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
T
Tournament API
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Kata
Tournament API
Commits
a5588a1d
Commit
a5588a1d
authored
5 months ago
by
Clément CORNU
Browse files
Options
Downloads
Patches
Plain Diff
feat: final update of README.md
parent
ab0f7c1d
No related branches found
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+5
-6
5 additions, 6 deletions
README.md
with
5 additions
and
6 deletions
README.md
+
5
−
6
View file @
a5588a1d
...
...
@@ -151,9 +151,8 @@ this API.
Concurrency is currently not handled by the API : if 2 users try to update the same player's points at the same time,
the update could return inconsistent data. We could for example use a versioning on player entity to set it up.
-
change score computing
-
add checkstyle
-
...
-
open api
-
Itest
regarder les contraintes
\ No newline at end of file
We also have no pagination on finding players : this could be a good improvement in the case of dealing with large
amount of players.
Finally, one last improvement we could make is to handle transactions. This is permitted by AWS SDK but would require
some refactoring inside the Repository layer.
\ No newline at end of file
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment