You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
getLocalizedFields is fairly complicated. Over time, support is added for multiple Payload field types such as group, array, blocks ...etc.
Because we are writing our own logic for this, bugs can creep in that are hard to detect! For example, consider what might happen if fields are added that get detected as localized when they shouldn't be - #64.
On the one hand, it makes sense to have our own function - we need to be involved in the recursion to control:
which fields are sent to fields.json;
which fields create their own html files; and
which fields are excluded.
However, https://github.com/payloadcms/payload should be studied to see if there is any logic that can be used to make this functionality more maintainable/reliable.
The text was updated successfully, but these errors were encountered:
getLocalizedFields
is fairly complicated. Over time, support is added for multiple Payload field types such asgroup
,array
,blocks
...etc.Because we are writing our own logic for this, bugs can creep in that are hard to detect! For example, consider what might happen if fields are added that get detected as localized when they shouldn't be - #64.
On the one hand, it makes sense to have our own function - we need to be involved in the recursion to control:
fields.json
;html
files; andHowever, https://github.com/payloadcms/payload should be studied to see if there is any logic that can be used to make this functionality more maintainable/reliable.
The text was updated successfully, but these errors were encountered: