Flask is implemented, however the code base is a bit unorganized. Both from a execution standpoint (running the application), and from a code standpoint (proper set/get functions, removing test functions, etc)
We will proceed with this work in small steps, and not one giant PR. Big PRs make it harder to catch issues.
Things to work on:
Error handling in Sorcery_API.py
Moving functions around to proper files
Re-imagining the sorcerybook and sorcery classes and their relationship to your DB
Remove or move hard coded spell/spellbook generation
Writing a README file for how a user can run your code
ETC
For each item, schedule some time to talk to me so we can walk through what I mean for each item, that way we can determine the actual work that needs to be done(if any) for each one.
By doing this work, you will accomplish the following:
A user can easily take your code and get it running
Your code is well organized and easy for a peer to pick up and start contributing to
Your API code can handle any/most scenarios and return errors that won't crash your program
Flask is implemented, however the code base is a bit unorganized. Both from a execution standpoint (running the application), and from a code standpoint (proper set/get functions, removing test functions, etc)
We will proceed with this work in small steps, and not one giant PR. Big PRs make it harder to catch issues.
Things to work on:
For each item, schedule some time to talk to me so we can walk through what I mean for each item, that way we can determine the actual work that needs to be done(if any) for each one.
By doing this work, you will accomplish the following: