-
Notifications
You must be signed in to change notification settings - Fork 331
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Roadmap #4287
Comments
Does this roadmap apply to all Mesh packages? I assume all the packages will start following Semantic versioning once all the issues in the V1 list are complete? |
After v1, we will follow semantic versioning in all packages. No breaking changes will be introduced in any minor and patch releases. |
Has support for react native been considered? |
@alberthuang24 Could you explain more about React Native support because currently GraphQL Mesh can be used as a client inside React Native? |
I'm using graphql-mesh as a client in react native, but it triggers an error |
If it is confirmed that |
This issue is for the Roadmap :) could you create a seperate issue ? |
At The Guild we’ve decided to work as much as we can in public, that’s why we are opening the roadmaps for all of our projects.
The goals for this are:
v1
v1.x
requiredSelectionSet
#4361connectionParams
to downstream also inconnectionParams
#4305mode
default + support all transforms on all sources #1930argTypeMap
no longer takes custom types #2881The script will never generate a response
on Cloudflare Workers. #4201json-machete:0.9.0
breaks on Windows when loading local files #4094@resolveTo
directiveIssue to triage
string
parameters excluded withexplode: true
#4677explode: true
with strings #4678connectionParams
to operation context and introduceconnectionParams
option for graphql handler #4724additionalResolvers
&additionalTypeDefs
#4847The text was updated successfully, but these errors were encountered: