Add API Implementation to Wiki #192
Labels
No labels
_CRITICAL_
API
app
backEnd
Blocked, waiting for further changes
bug
cleanup
close
design
duplicate
enhancement
feature request
frontEnd
help wanted
invalid
low priority
needs input
needs review
project documentation
question
research
reviewed
script
security
SQL
style
testing
topLevel
wontfix
No milestone
No project
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Andras/BoundlessFlowCampus2K#192
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We need to standardise how we handle API calls and implementation. This should be added to the top of this page
Done writing Api Wiki . Needs review
Documentation is Understandable and looks good, There are no changes needed and no major error, there is a small missed " in data structure code example
Suggestion:
i would suggest including a picture example of entries in the JSON file in the form of a table for the header data. Right now you show the index values and their corresponding column header names, which is good, but a second picture example showing a row entry that includes every column could help clarify structure
okay, looking in to it
Noticed that the wiki contained outdated Api documentation . Working on re writing it.