- π«π·France Grimreaper France π«π·
The import error is related to π¬ Call to a member function getAlias on null Fixed .
Here let's focus on the diff problem.
- Issue was unassigned.
- Status changed to Closed: cannot reproduce
over 1 year ago 11:03am 17 February 2023 - π«π·France Grimreaper France π«π·
Hi,
I am sorry, but I cannot reproduce the warning in the diff. See the attached screenshots.
I used the list field used in the tests:
- https://git.drupalcode.org/project/entity_share/-/blob/8.x-3.x/tests/mod...
- https://git.drupalcode.org/project/entity_share/-/blob/8.x-3.x/tests/mod...I think it matches your requirements.
After first successful try, I put cardinality to unlimited to check if this could be the source of the problem, but it was also ok.
If you witness this issue on "real" content, maybe between the moment you imported a content for the first time, and the moment you want to check the diff, you made some changes in the JSON:API output with JSON:API Extras field enhancer or something else and so the output is not the expected one for the diff.
"field_es_test_list_text": [ "choice_1", "choice_2", "choice_3" ],
By default it should be the keys that are exposed so if you have the same keys between your website it should be ok.
When writing the comment, I have an idea, let met check if it is possible to have keys with spaces or special characters, maybe that's the problem source.
- π«π·France Grimreaper France π«π·
I tried with configuration:
choice_1|Choice 1
choice_2|Choice 2
choice_3|Choice 3
age5-12|Ages 5-12
age13-17|Ages 13-17
foo bar|TestThe JSON:API output:
"field_es_test_list_text": [ "choice_1", "choice_2", "choice_3", "age5-12", "age13-17", "foo bar" ],
See the diff output in the attached screenshot.
- π«π·France Grimreaper France π«π·
Feel free to re-open if able to provide steps to reproduce starting form a fresh Drupal install.