-
Notifications
You must be signed in to change notification settings - Fork 217
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add sample handler and docs for non-JSON body #977
Merged
Merged
Changes from 52 commits
Commits
Show all changes
60 commits
Select commit
Hold shift + click to select a range
0d2612e
Return handlers from install
eddyashton d50db07
Set some fields _after_ install
eddyashton c4725b5
Add setter methods
eddyashton 3942aeb
set_auto_schema as a method
eddyashton 92573d0
Remove use of install_with_auto_schema
eddyashton ff77000
Remove install_with_auto_schema
eddyashton 64d71af
Missed some
eddyashton 867c3e6
Merge branch 'master' into simple_install_signature
eddyashton 5b30275
Document Handler& return
eddyashton 1e69b7c
SNIPPETs for install_get
eddyashton 4761ed1
Add initial verb restrictions adapters
eddyashton 5ba0963
Add ALLOW header, sort headers
eddyashton afa26c9
Unit test for verb restrictions
eddyashton 93f7c68
Merge branch 'master' into verb_selection
eddyashton 5de1570
Ignore body of GETs
eddyashton 652fa4d
Fix whitespace
eddyashton f395cee
params are moveable!
eddyashton 55fb9c8
who_am_i is get_only
eddyashton f45d5df
Specify verb for Python clients
eddyashton df61440
Neater formatting
eddyashton 624dc75
Make some more endpoints get-only
eddyashton 1284226
Remove some empty params, add GETs
eddyashton a52a6cc
Replace .do with .rpc
eddyashton d96abfd
add client.get
eddyashton 88bafe7
Bite the bullet - add a url-unescaper
eddyashton 17cb907
Unescape queries, test
eddyashton fffd835
Send escaped query URLs
eddyashton c678899
getCommit from Python is now a GET
eddyashton 3f8ee8e
getQuotes is GET-only
eddyashton 71c10cc
get-only is a Handler-method, not an adapter
eddyashton c7074b6
Match uses of GET
eddyashton 7f90438
Remove more empty params
eddyashton 393e9be
?
eddyashton 927ba26
Correctly format query in canonicalisation!
eddyashton 1a70e89
Whoops
eddyashton ac11b56
Merge remote-tracking branch 'origin' into verb_selection
eddyashton b894098
Fix elections tests
eddyashton d62a239
Use bit mask to represent allowed verbs
eddyashton a679881
Compiles
eddyashton 03e0dcf
Check that failing verbs AREN'T included in ALLOW header
eddyashton dbf7a6f
Merge remote-tracking branch 'origin' into verb_selection
eddyashton abecc8a
Merge branch 'master' into verb_selection
eddyashton 8e9408c
Use timeout!
eddyashton d16eb8b
Add log_record_text (non-JSON body)
eddyashton 0106126
Install
eddyashton a0b1bb6
Basic test
eddyashton f8b210c
Merge branch 'master' into non_json_body_sample
eddyashton 9509fea
Support header-defined payload-types through clients.py
eddyashton 71defbb
Update docs
eddyashton 1811f18
Grammar fixes
eddyashton 3391a43
Re-enable other logging tests
eddyashton a3539d1
Merge branch 'master' into non_json_body_sample
eddyashton 95aa75b
LOG_gets are GET-only
eddyashton a4d39cb
Merge branch 'master' into non_json_body_sample
eddyashton 58df585
Fix scenario test
eddyashton 5dd463f
Set return type for jsgeneric
eddyashton 6d94ae5
Pass query to JS
eddyashton 4102995
LOG_get in JS parses query
eddyashton 3786baa
Merge branch 'master' into non_json_body_sample
eddyashton 1487f5c
Formatting
eddyashton File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if it's worth adding a new page/section that describes the different types and options on handlers without mentioning the logging app specifically? I think we'll need one sooner or later to describe the different types/flags on handlers. We could always link to the logging app as examples (with back links too). Thinking about it, we should doxygen
handlerregistry.h
and get most of this for free. What do you think?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree! This is where we should aim, ideally with most of this coming 'for free' from doxygen. I think the next step is to split the thing apps see from the thing the framework sees (ie - they get an opaque
Handle
with the methods, we see the raw struct state), then the app side gets doxygen'd.Naming is awkward - what's a 'handle' for a 'handler'? Maybe we should go more HTTP-heavy and talk about installing resources or endpoints rather than RPC handlers?
Anyway I think this is all future work.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
doxygen + links is absolutely the way to go! For naming, I think we should pick a popular framework, align, and reference explicitly.