A way for plugins to manage library definitions about js-graphql-intellij-plugin HOT 2 OPEN

Hi @BoD! How will you provide a schema file in your plugin? Will you follow the same approach as the GraphQL plugin?

from js-graphql-intellij-plugin.

This is to be determined - but I think the most flexible way would probably to have an API that takes a String as an input, so a plugin could programmatically build this String to handle different cases.

To give your more context, in Apollo Kotlin (and other Apollo tools) we have a generic @link mechanism where a schema can declare to import certain definitions. You can read more about it here. We intend to leverage this mechanism in the future any time we need to add new definitions.

So for instance, in v4 we are adding a new directive @catch, and for users to use it, they'll have to import it this way:

extend schema @link(
  url: "https://specs.apollo.dev/nullability/v0.1", 
  import: ["@catch", "CatchTo"]
)

When doing this Apollo Kotlin will add the @catch directive to the user's schema so it can be used in queries.

The ultimate goal for us would be to have support for this mechanism in the plugin. So when @catch is imported via @link, then it should be recognized in the editor.

I hope this makes sense :)

from js-graphql-intellij-plugin.