yakup-jr/score-sentinel

It will help you spend good time not doing calculations play in different games

score-sentinel

score-sentinel's Issues

fix(portal): define root migration

• define root migration
• update changeset

feat(ss-portal): init ss-portal module

Here we can go

Tasks:

• init ss-portal module using spring
• add spring security
• add data-jpa
• add hateoas
• add liquibase
• add starter-test
• add lombok
• add junit
• add devtools
• add h2 database
• add postgresql

refactor(roles): refactor roles module

feat(portal): add match module

Use TDD (#30)

Need create match entity, which will have name, id, teams, score, game, result. Now we don't have result. It should be entity, which will include teamId, matchId, score, points.

Aslo should be define except entity, model, service, controller, exception but and advice for exception, link on match.

Finally should think about DTO or something like this (optional).

test(roles): test roles module

• test roles repository

test(team): add team test

• add repository test

feat(initialization): init spring application

In this project will use multi module and because in root module won't include any dep.

Tasks:

• init spring root module
• add lib to .gitignore

refactor(team): refactor team module

For improve code quality should be:

• define DTO for request and response by controller

feat(team): add team module

• add entity
• add model
• add repository
• add service
• add exception
• add controller
• add link builder

test(match): add test repository

Firstly should write test before code. Repository test should be write not only for match entity but and for matchResult

feat(user*roles): add migration

• update changelog_version-1.0.h2.sql: add games schema
• update changelog_version-1.01.h2.sql: update reference to games table
• add changelog_version-1.1.h2.sql: migration for users and roles

test(user): test user module

• test user repository

add service test

feat(ss-portal): add game module

In out service will calculate points and other param. But now we don't have necessary entity for use full plan games. So for this stage module should define two properties:

• name: String

• id: Long

• This properties should define in changelog using liquibase.

• Aslo on this stage should turn off spring security x-csrf.

• For this should defie property in application.property file as i think.

And about module should be create:

• entity
• model
• repository
• service
• controller
• exceptions

refactor(portal): refactor game module

• update GameController: split method into two
• update GameEntity: delete @builder, @slf4j
• update GameModel: add lombok
• update GameNotFoundException: compliance with SRP
• update GameRepository: fix @query's requests
• update GameService: split method into two

refactor(user)

feat(portal): transition to real db

Need transition to real db. So just need update application.properties

test(portal): add game test

• add repository test

feat(roles): add roles module

Need add roles module which will uses user module but this module should be define as undependency module because in future it can use not only in user module

feat(portal): add user module

In this case should be define some step:

• add user entity
• add user model
• add user repository
• add user serivce
• add user controller
• add user exception