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.
This should add a simple demo of the rest handler. It bear bones as I understand we do not have any specific convention here. Though feel free to let me know if there is anyway I can amend it.
I could of added something like a list that gets modified each time by put or delete. Though I just don't quite have my head around managing states between connections of different type. The rest example for the most part is stateless due to their not being an API token associated with request.
There is likely other methods through default request headers but I felt the need to not over complicate things here.
I was concerned about not having redirects though I realized the API should be accessible by a HTTP client. The
curl
with the response being returned to the application.Any tips or advice on how to improve this & make it more compatible would be more than welcome.