-
Notifications
You must be signed in to change notification settings - Fork 26
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
feature/progressive-function-extractors #190
feature/progressive-function-extractors #190
Conversation
ndortega
commented
Apr 25, 2024
- added support for query params w/ default values
- Added support for Extractors
- Global and local validators for extractors
…ters from function and building structs from plain dictionaries (useful in queryparams and forms) 2.) added deps for the above feature and also included Revise for future autoreloading
…es from function signatures
… from the HTTP.Request object 2.) updated extractor tests
…o a route with no path params.
2.) added protobuf extractor & tests 3.) struct_builder now works recursively with deeply nested json and types
…-function-extractors
2.) Extrators are now defined utilizing a macro 3.) added a validate and type properties to Extractors
…pes from extractors
2.) removed unused code 3.) added more tests 4.) Added a TestPackage to load the oxygen as a dependency & included tests to run against it to check for precompilation issues
2.) updated readme docs
This errors on a following line in PeaceFounderAdmin:
Here
|
Hi @JanisErdmanis, Thanks for the error report. It looks like my reflection code is trying to parse a CodeInfo object that represents the main body of a function. Oxygen only cares about the function signature, so I've added some checks to try to skip everything else. Clearly, this check isn't working as intended - I'll have to see why its failing in this case. Feel free to actually open an issue for this since this will probably affect other package authors. I've also added a new test package in this update to check for precompilation issues. Once I figure out the reason, I'll try to recreate that case inside that test package |
Hi @JanisErdmanis, I've updated the piece of code that's causing this issue and opened a PR. Can you manually test this branch and let me know if the issue still persists PR: #192 |
This fixed the error, and everything else seems to work as expected. |