Playground additions and switch to SQLite for playing #8
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
…tabase; applied migrations to it
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.
I did several things just to make playground friendlier:
1 - use SQLite instead of MSSQL. db file is provided with PR, I added some entities in it, so users can have something to play against. MSSQL is pretty big beast!
2 - use Swagger in ToyFactory project, so people can explore nice UI instead of writing requests in Postman or other programs
3 - added several controllers, tecture services etc; so each entity in DB can be added/viewed at least
I tested branch on addition of all entities (not all methods at the time). Tests wont work for now, because I changed most realizations of services.
TODO: create some readme for playground with basic depiction of db schema and tecture usage