Open GustavTaxen opened 9 months ago
Hi, thanks for getting in touch! Are you asking for a sourceId
to be returned in your query? If yes, then you should change that to canonicalId
to get rid of the deprecation error.
No, we don't ask specifically for a sourceId in any of our GraphQL queries. We ask for id
in many of them, though.
On 31 Jan 2024, at 15:57, Iwona Just @.***> wrote:
Hi, thanks for getting in touch! Are you asking for a sourceId to be returned in your query? If yes, then you should change that to canonicalId to get rid of the deprecation error.
— Reply to this email directly, view it on GitHub https://github.com/craftcms/cms/issues/14254#issuecomment-1919274168, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACSCUSLASS6IZCAFAE574JLYRJLWJAVCNFSM6AAAAABCSSJOVSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJZGI3TIMJWHA. You are receiving this because you authored the thread.
Thanks for confirming. I’m unable to replicate this, nor can I see any references to sourceId
that could cause this in Craft’s code. Could you please share one simple query that results in the deprecation warning being logged (along with info on what element types and fields are used in it)?
What happened?
Description
We get this deprecation warning in the control panel. Does this mean that we using the GraphQL API incorrectly?
Craft CMS version
4.6.1
PHP version
8.1.27
Operating system and version
Linux 4.15.0-197-generic
Database type and version
MySQL 47
Image driver and version
Imagick 3.7.0 (ImageMagick 7.1.1-13)
Installed plugins and versions