Roadmap to v1.0?

[yann-combarnous]

Hi,

I love this package, but still feel there would be a couple of steps to reach maturity and broaden adoption. I would love to see it reach 1.0.0 milestone, ie provide a stable major version.

Here are some ideas of what could be added to reach 1.0 milestone:

• setup documentation: a lot of features are still buried in discussion, code, issues, 2 simple examples: environment variables in config file %{MY_ENV} and the ability to load custom transforms or handlers. 2 great features, but missing from documentation. Would be great also to have recommended architecture, ie ideas to integrate mesh in existing environments.
• code samples and sandboxes: it would be great to have code sandboxes to demonstrate each feature in documentation. It exists for a couple of pages, but not systematically
• add sandboxes in doc to regression tests: per issue 1156, it seems some existing code sandboxes have issues
• add a user-friendly CHANGELOG.md file: current dependency system make it hard to check release feature history, as it is very verbose and propagates dependency across all packages
• add ROADMAP.md: provide clarity on priorities for next 3-6 months
• enhance error reporting: add debug levels and verbosity, better checks for meshrc
• add CONTRIBUTE.md: provide guidelines for code contributors
• add PR and issue templates

Any roadmap on your side to reach 1.0?

[Urigo]

@yann-combarnous thank you so much for this!
We should definitely create a public roadmap.
In the meantime, any help with the points above would be great!

[Davenporten]

Has there been any development of that roadmap? I've been using graphql-mesh for around 6 months now and have really found a lot of value, but my manager is wary of the fact that it still isn't at 1.0 yet.

[Urigo]

We've just released a huge refactoring for the library!
Please update and check out the new commands and docs.
By the way, I also recommend you to use RenovateBot to keep your dependencies up to date and also watch this repository on GitHub using GitHub Notifications as there are a lot of things happening constantly...

About releasing 1.0, with the new refactoring we've made most of the things we wanted to change happen, but we want to give it a bit more time for feedback from the community.
We also want to improve the docs a lot.

But in terms of features and support, you can feel comfortable to rely on this library, like any other library from @the-guild-org

[Davenporten]

Thanks @Urigo, that's great to hear, I will check it out!