-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Added remote-schemas document in Marathi Language #9944
base: master
Are you sure you want to change the base?
Conversation
Beep boop! 🤖 Hey @Atharva1723, thanks for your PR! One of my human friends will review this PR and get back to you as soon as possible. Stay awesome! 😎 |
Marathi is predominantly the key language spoken in the majority of parts of North India. So the Documents should also be translated to Marathi. |
Hey @Atharva1723! Thank you for your contribution and for taking the time to submit this PR. ❤️ Upon reviewing your PR, we’ve noticed that it may not align with our current project priorities or needs. However, we encourage you to keep contributing, and we’d be glad if you could explore the current Hacktoberfest Top-N Challenge. If you have any questions or need guidance, please don’t hesitate to ask. Once again, thank you for your support and commitment to open source! 🚀 |
Description
This pull request adds the Marathi translation for the "Remote Schemas" document. The document has been fully translated into Marathi to make it accessible to Marathi-speaking users. Please review the changes and consider merging them to provide Marathi-speaking users with access to this valuable information in their native language.
Changelog
Component : server / cli / console / build
Type: bugfix / feature / enhancement
Product: community-edition
Short Changelog
Long Changelog
Related Issues
Solution and Design
Steps to test and verify
Limitations, known bugs & workarounds
Server checklist
Catalog upgrade
Does this PR change Hasura Catalog version?
Metadata
Does this PR add a new Metadata feature?
run_sql
auto manages the new metadata through schema diffing?run_sql
auto manages the definitions of metadata on renaming?export_metadata
/replace_metadata
supports the new metadata added?GraphQL
Breaking changes
No Breaking changes
There are breaking changes:
Metadata API
Existing
query
types:args
payload which is not backward compatibleJSON
schemaGraphQL API
Schema Generation:
NamedType
Schema Resolve:-
null
value for any input fieldsLogging
JSON
schema has changedtype
names have changed