Handle non existing field on client website

Created on 28 August 2018, about 6 years ago
Updated 3 January 2024, 9 months ago

It's written that entities on server and client have to be identical but what is the main reason ?
It should be possible to save an incomplete entity on the client if fields are not exist.

Feature request
Status

Fixed

Version

3.0

Component

Code

Created by

🇨🇭Switzerland OlivierG

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇦🇺Australia JDSaward

    @Grimreaper, your suggestion of 5 years ago works really well, server is D9, Client is D10.

    'You can play with the features of JSON API extras to disable fields on the server website.'

  • 🇨🇳China lawxen

    On the server side, jsonapi_extra rewrite a field name, like name_a==>name_b
    But the client check if it has field name_a.
    This seems like wrong logic. It should check if client has field name_b.

  • 🇨🇳China lawxen

    Created an new issue to fix it.

Production build 0.71.5 2024