-
Notifications
You must be signed in to change notification settings - Fork 98
docs: Document new functional API #2282
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
Conversation
leandrodamascena
left a comment
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.
Hi @phipag, overall, this PR seems great to me. I'm just wondering if it makes sense to refer to the Functional API as recommended way and the annotation as legacy mode.
If you think that make sense, then make changes.. If not, ignore my comments and I can approve.
Co-authored-by: Stefano Vozza <[email protected]>
Co-authored-by: Stefano Vozza <[email protected]>
Co-authored-by: Stefano Vozza <[email protected]>
Co-authored-by: Stefano Vozza <[email protected]>
Co-authored-by: Stefano Vozza <[email protected]>
Co-authored-by: Stefano Vozza <[email protected]>
Co-authored-by: Stefano Vozza <[email protected]>
Co-authored-by: Stefano Vozza <[email protected]>
Co-authored-by: Stefano Vozza <[email protected]>
Co-authored-by: Stefano Vozza <[email protected]>
Co-authored-by: Stefano Vozza <[email protected]>
|
1 similar comment
|



Summary
This PR adds the new functional interface introduced with v2.6.0 to the documentation highlighting for all utilities that there is now an alternative way that does not depend on AspectJ anymore. The key benefits of this are:
handleRequestmethod signature anymoreWe also add a new "Usage patterns" page similar to TypeScript.
Preview available here: https://dealn7fl31ram.cloudfront.net/
Changes
Issue number: #2221
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.