Currently REST Views displays cannot make use of Header or Footer areas. These are commonly used for typical HTML views to feature information about the first row, add aggregation data, or simply inject arbitrary content. The same is also needed in collections, such as introducing result counts or adding a "version" property.
Add support for Header Areas or a new type of views row plugin that allows one or more properties to be added to the view for merge into the collection structure.
Identify path forward, implement.
This would open up new options in the Views UI. This would allow additions to REST collection output.
These are not breaking changes, except in anti-pattern API clients that fail on unrecognized properties in data payloads.
?
None.
Postponed: needs info
11.0 🔥
rest.module
Related to the Views in Drupal Core initiative.
Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.
Enhances an existing API or introduces a new subsystem. Depending on the size and impact, possibly backportable to earlier major versions.
A change record needs to be drafted before an issue is committed. Note: Change records used to be called change notifications.
To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
No activities found.