-
-
Notifications
You must be signed in to change notification settings - Fork 714
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 /ok route as an express middleware #4432
Conversation
✅ Deploy Preview for volto ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Passing run #6383 ↗︎
Details:
This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. |
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.
In Plone the ok view is namespaced by the @@
symbols, so there's no chance to overlap something else. Let's do something similar here. Maybe /_ok
?
Also, I don't think there's a need for a setting for this, if we solve the namespacing problem.
@plone/volto-team thoughts on this?
How about something like Whatever it is, it should be mentioned in the docs. |
Well, it also works with |
I would also keep using the |
We need a consensus here. I'm ok with using both |
I'm +1 on adopting the industry standard. |
I don't see a ok URL under the well-known URLs right? I mean I don't mind using the .well-known approach, but right now there's no such standard for ok right? We can start having the ok like we have in classic and evolve to whatever is stablished later on. |
I was the one who brought up the |
Would that go here? https://6.docs.plone.org/volto/configuration/settings-reference.html#server-specific-serverconfig |
@erral @stevepiercy yes, good for me. Let's add some docs and merge. |
I have realized that I was missing the documentation part on this PR as requested by @stevepiercy 🤦 so I have added it 😉 |
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.
Thanks for the docs. Mostly MyST and English syntax and grammar.
thank you as always! |
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.
It is OK to ignore the failing docs job. He Who Shall Not Be Named has once again pulled more feathers from the bird site, now requiring authentication to view a user's twerks. |
Co-authored-by: ionlizarazu <ilizarazu@codesyntax.com> Co-authored-by: Víctor Fernández de Alba <sneridagh@gmail.com> Co-authored-by: Alin Voinea <contact@avoinea.com>
* master: (42 commits) make selectedView and className props available for Search block (#4997) Release @plone/volto-testing 4.0.0-alpha.0 Release 17.0.0-alpha.21 Upgrade to Cypress 12.17.1 (latest) (#4981) Image rendering (#3337) feat(Url.js): add getFieldURL helper function to get the url value of a field based on its structure (#4731) Handle @linkintegrity response with items but no breaches (#4832) Release 17.0.0-alpha.20 Use all the apiExpanders in use, so we perform a single request for getting all the required data. (#4946) Fix the condition deciding on listing pagination format so it takes into account container blocks as well (#4978) Release 17.0.0-alpha.19 Fix search block input clear button doesn't reset the search (#4837) Add /ok route as an express middleware (#4432) handles condition for yearly frequency in recurrence (#4604) Remove dangling out of place Guillotina Cypress tests (#4980) Update to latest plone.restapi and Plone 6.0.6 (#4979) Update browserlist (#4977) `Links and references` view via content menu [Add `Links to item` view] (#4787) Release 17.0.0-alpha.18 Toc responsive (#4912) ...
Fixes #4375 adding an Express middleware
This supersedes #4429