5.x Working Roadmap

[acao]

Hey so!

What does the roadmap for the rest of 3.x look like?

I have some ideas for the programattic API and other feature improvements. Do you all mind if i start turning this issue into a legit roadmap?

[kamilkisiela]

Feel free :)

[dimaMachina]

I propose for GraphQL Config v5 the followings

• drop Node 12 support
• remove the legacy structure of config and legacy config names
  
  
• bundle to ESM only
• support graphql.config.mjs config

[acao]

@B2o5T we still have many users who need the legacy mode because intellij‘s graphql config is still entirely based on 1.0 config.

For example at my company we use the legacy graphql config format because a majority of developers use intellij IDEs.

we still regularly get support issues like this where people find they have to toggle on legacy support

[acao]

A few features that would be nice for the LSP server, and allow us to rely on this library‘s internals rather than our own DIY normalization of the raw config:

• I would like getDocuments() to have an option for CodeFileLoader to continue after parse failures, but perhaps we can use loadDocuments() and pass an option for this?
• It would be great to have a project.getEndpoints() that normalizes and returns endpoints and config. If no extensions.endpoints are configured, it attempts to retrieve this information from the schema config
• project.getSchemaFiles() would return a normalized list of all the files with SDL in the schema config