Ben Asher

Ah, thanks @andrewbranch! @khanayan123 is that enough info for your team to fix? (started working on it myself, but it turned out to be more significant than I think it...

@khanayan123 I took a crack at it in #3937, but there's one outstanding issue. @andrewbranch I have the namespace merging set up, but when I attempt to use it in...

Thanks for the tip! That suggestion definitely makes sense (i.e. value vs type). I pushed an update and rearranged the diff a bit. It should be easier to read now...

You were right — [sneaky one](https://github.com/DataDog/dd-trace-js/pull/3937/commits/22218d58f7bb52e542114d823b8eea54e911e609)!

Maybe this is a FlatConfig-specific thing? I can't reproduce this in the example project, but I can definitely reproduce it in ours.

Confirmed this reproduces in the multiple-project sample project. It doesn't reproduce today because both schemas define a User type. If you just change one of them to be called AdminUser...

It's reproducible in the sample project in this repo. See this patch: https://github.com/dimaMachina/graphql-eslint/issues/2260#issuecomment-2070092469

if you set parser as the following, it seems to work as a workaround: ``` parser: { ...graphqlEslint, meta: { name: "@graphql-eslint", } } ```

Would love to see this! We'd like to use this package to check our final frontend build, and most frontend builds these days are ESM (including ours)

The plugin also throws an error if used with FlatConfig compatibility helpers. Even if it doesn't natively support FlatConfig, it would great to fix that in the interim.