Closed sezaru closed 4 months ago
AFAIK this is fixed in 3.0. Do you need a back port fix or can you wait to update to 3.0 for the fix?
We do plan to upgrade to Ash 3 in the next few weeks, so for now we can just "duplicate" the resource in the other API as a workaround. Thanks!
Describe the bug This bug is for a project that I haven't update to Ash 3 yet, so I'm not sure if the same bug is reproducible in Ash 3 with the latest version of Ash Graphql.
Adding a resource that is used by AshGraphql in two or more APIs, will break compilation.
To Reproduce Have a resource that has
AshGraphql.Resource
extension, then add it to two different APIs which also usesAshGraphql.Api
extension.During compilation, it will fail with a bunch of errors like this one:
Expected behavior I think that AshGraphql should identify that the resource is the same and work with multiple APIs
** Runtime