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
Currently the support in Drupal core to create translations and revisions is limited. There is a 3-years old discussion on how to implement this in JSON APIs with no clear solution foreseen since it has implications to the Drupal core: mainly because it is difficult to handle all edge cases in a generic way. Moreover, now JSON API is part of the Drupal core and we cannot just patch the module because it may block future core (security) updates.
Therefore the solution suggested is to create our own custom REST endpoint which allows handling both multilingual an revisions according to the project needs. Later, if there's another solution provided by the Drupal core, these endpoints can either be removed or preserved as a thin layer between the external tool and core REST API. Even so, the solution provided would be lightweight since it will handle exactly our use-case and it doesn't require to be generic.
Currently the support in Drupal core to create translations and revisions is limited. There is a 3-years old discussion on how to implement this in JSON APIs with no clear solution foreseen since it has implications to the Drupal core: mainly because it is difficult to handle all edge cases in a generic way. Moreover, now JSON API is part of the Drupal core and we cannot just patch the module because it may block future core (security) updates.
Therefore the solution suggested is to create our own custom REST endpoint which allows handling both multilingual an revisions according to the project needs. Later, if there's another solution provided by the Drupal core, these endpoints can either be removed or preserved as a thin layer between the external tool and core REST API. Even so, the solution provided would be lightweight since it will handle exactly our use-case and it doesn't require to be generic.
References:
The text was updated successfully, but these errors were encountered: