Bug description
Not sure if this behaviour is an issue or not, but when using the entries field on globals, does not yield to the same REST API output as using the same field in collections.
When used in globals and the content is fetched via the REST API, I get only an array of item IDs.
When used in collections I get the small object with the properties: id, title, url, permalink, api_url
How to reproduce
Create a global blueprint with the entries fieldtype.
Add the entries field type to a blueprint.
Fill in the entries and call them via the REST API endpoints, and they are not the same.
Logs
No response
Environment
EnvironmentApplication Name: StatamicLaravel Version: 10.15.0PHP Version: 8.2.7Composer Version: 2.5.4Environment: localDebug Mode: ENABLEDURL: ***Maintenance Mode: OFFCacheConfig: NOT CACHEDEvents: NOT CACHEDRoutes: NOT CACHEDViews: NOT CACHEDDriversBroadcasting: logCache: statamicDatabase: mysqlLogs: stack / singleMail: smtpQueue: syncSession: fileStatamicAddons: 1Antlers: runtimeStache Watcher: EnabledStatic Caching: DisabledVersion: 4.11.0 PRO
Installation
Fresh statamic/statamic site via CLI
Antlers Parser
None
Additional details
No response
Bug description
Not sure if this behaviour is an issue or not, but when using the entries field on globals, does not yield to the same REST API output as using the same field in collections.
When used in globals and the content is fetched via the REST API, I get only an array of item IDs.
When used in collections I get the small object with the properties: id, title, url, permalink, api_url
How to reproduce
Create a global blueprint with the entries fieldtype.
Add the entries field type to a blueprint.
Fill in the entries and call them via the REST API endpoints, and they are not the same.
Logs
No response
Environment
Installation
Fresh statamic/statamic site via CLI
Antlers Parser
None
Additional details
No response