Your task is to create an application, that will enable the user to move chess pieces on a chess table, using REST API.
- Chess table is always 8x8 and each field can be described as a tuple e.g. (3,0), both values can be int, there is no need to keep the original chess position naming like "A4".
- On a single field there can be always only a single chess piece (pieces are of the same color so they can't interact with each other).
- There are only two possible chess pieces: rook (The rook moves horizontally or vertically, through any number of unoccupied squares) and bishop (The bishop moves diagonally in any direction it wishes and as far as it wishes as long as the squares are free).
- Each piece can be removed from the table, but we need to keep its last position, a piece that was removed can't be placed on the table again
- There should be a possibility to put a new piece (of a given type) on an empty chess field and assign a unique ID (you can choose how ID should look like) to it during this action.
- There should be a possibility to move a piece to a selected field given an id of the chess piece that is on the table.
- Use this repository as a backbone to implement functionality under the '/application' directory.
- To implement REST API, please use ZIO and Tapir (application should also host swagger)
- You are free to choose how to persist the data, but the application in case of the unexpected crash should not lose the state of the chess board or any previously created chess piece
- Each successful action should be emitted to Kafka "events" topic (adding piece, removing piece, moving piece)
- Feel free to extend Dependencies.scala but keep in mind that using Scala, tapir, ZIO and kafka is mandatory!
For convenience and easier testing, you are provided with /client which should read and log all messages that were sent to the configured topic. Also, you can use file under /docker-compose to set up Kafka for testing the implementation. If you need feel free to extend compose file.