Adria within the community mentioned creating two models, modelA and modelB. modelB contains a reference to modelA, and if modelA is updated, modelB's reference to it shows outdated fields.
I believe modelB should have the current reference to modelA.
modelB will point to the first publishing of modelA.
/cms/read/environment that you are usinglistGenres and you will see an outdated reference to BookIf you republish Genre, it will contain the updated reference to the latest publication of Book.
we should make the link to the latest revision of the Book instead of the previous one.
We should update our test cases: refPublishingEntries.test.js within api-headless-cms so that it tests this updated and expected behaviour.
Yeah, we should store parent IDs when storing these references, not the exact revision ID.
Hello, just wanted to say that we've run into this exact problem and would love it if the parent ID could be stored instead of a revision ID. Thanks!
I just linked a PR that will fix this. Should go out today / tomorrow @jacqui.
I just linked a PR that will fix this. Should go out today / tomorrow @jacqui.
Amazing, that was so fast @doitadrian! Thank you.
Hey @jacqui, 4.10.0 was released yesterday.
Please check the https://github.com/webiny/webiny-js/pull/1204 (the Blog section at the bottom of the PR body) for details about the feature and further steps.
And let us know if you have any questions, thanks!