Closed WilkinsonK closed 2 months ago
I really don't like the idea of naming the new oxinat_core
sub-module api
. Current working list of alternatives are:
What we are really doing with this story is setting up the intermediate layer between the top-level crate and the operations that are most commonly performed-- at least with the design intention of oxinat
.
As a developer using this library suite, I would like to have implementations predefined for most common data queries. That is, I would like to have an integration between the defined models and their appropriate REST GET calls.
We will want getters for the following, in order of priority:
There are other models that have appropriate GET calls available to them according to their API documentation, however they are not a priority for this story and can be dealt with at a later time.