Initial framework for inventory REST API and item reservations #3
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.
These changes contain a documented REST API utilizing the postgresql DB to add and update both fungible and non-fungible inventory items. These changes also include the beginnings of an item reservation system.
Two item reservation concepts exist. When a non-fungible item is reserved, it receives a timestamp of when it was reserved. The reservation on a non-fungible item can be removed, it can expire, or the item can be sold. A fungible item reservation works differently. Fungible items receive a series of reservations containing a timestamp and a quantity. The fungible item reservation also includes a session value to track the user it belongs to, however, this is currently being defaulted to null value. Fungible items total their reservation quantities for comparison against their amount_in_stock.