Text (formatted, long) no longer accessible directly via the query after upgrading to Beta1

[pavlosdan]

Previously in alpha7 a field (Text (formatted, long)'s value was directly accessible using:

{ fieldRichTextWidget }

now to get the same result one needs to do:

{ fieldRichTextWidget { value } }

even though the explorer reports that inside the 'fieldRichTextWidget' there is only a string. (please see screenshot)

[pmelab]

Did you add graphql_legacy?

This is on purpose (see the release notes, 2nd bullet. This behaviour is still available in graphql legacy, but the preferred way is to use the processed typed data property, which will provide the same result (and the trimmed text as well).

[pavlosdan]

No I didn't add legacy as it said it's not meant to be used: "These modules have been deprecated and should not be used."

Thought it may be better to rewrite the queries than using code that's deprecated.

[pavlosdan]

I see in Voyager the same field has the properties: processed, format and value. Shouldn't explorer have the same?

[pmelab]

Yes, they use the same data. Sounds like a caching issue to me.

[pavlosdan]

duh yes. cleared the browser cache and refreshed. yes now it reports the new properties!

[pavlosdan]

Thanks! closing this :)