- First commit to issue fork.
- Assigned to himanshu_jhaloya
- Issue was unassigned.
- 🇮🇳India himanshu_jhaloya Indore
Reroll #9 does not apply 10.2.x created the new patch and added the use statement please review
- Status changed to Needs review
9 months ago 1:44pm 15 February 2024 - last update
9 months ago Patch Failed to Apply - last update
9 months ago 182 pass - Status changed to Needs work
9 months ago 9:46am 16 February 2024 - 🇩🇰Denmark ressa Copenhagen
Thanks @himanshu_jhaloya. Manually attaching patches is being phased out, and you should create a patch and Merge Request with the Gitlab integration.
DrupalCI and all patch testing will be turned off on July 1, 2024 →
- First commit to issue fork.
- Merge request !106Issue #3097493: It is not possible to filter paragraphs via JSON:API. → (Open) created by joegraduate
- last update
7 months ago 182 pass - Status changed to Needs review
7 months ago 6:32pm 16 April 2024 - 🇺🇸United States joegraduate Arizona, USA
Created a MR that includes values for all of the
JSONAPI_FILTER_AMONG_*constants found in the example in jsonapi.api.php (not justJSONAPI_FILTER_AMONG_ALL). - last update
7 months ago 182 pass - 🇨🇭Switzerland berdir Switzerland
Ok, the All + Published version of this make somewhat sense, not quite sure about own, we don't have that context and I didn't dig deeper into when exactly each of those is used. But it's probably unlikely to be causing issues.
One thing to consider is that paragraph access is parent-inherited, so there is a chance that this could expose things that users could otherwise not see. A bit tempted to merge this due to that.
- 🇺🇸United States joegraduate Arizona, USA
@Berdir, do you think it would make sense to tie this functionality to a module configuration setting so that it is opt-in (disabled by default)?
Something like "Enable direct JSON:API access to Paragraphs"? (With a help text warning about the possibility of exposing content users could otherwise not see)