-
-
Notifications
You must be signed in to change notification settings - Fork 29
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 to v1.0 #179
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The goal for this plugin has always been to provide full feature parity with Gravity Forms, and as more users adopt our plugin it make's sense to outline exactly what that means and how to get there.
🎯 Release Goals
Below are the high-level goals for a 1.0 release:
Feature parity with Gravity Forms core.
Anything that Gravity Forms supports in PHP, our users should be able to do in a headless environment.
Stable API.
Users should be able to use the plugin without worrying about breaking API changes from release to release. While we can't prevent this altogether, v1.x should be robust enough that we don't need to push a breaking changes to the GraphQL schema for a long time.
"Bug free" and battle-tested.
For production sites, users need to know that everything works as expected. With the sheer amount that GF can do, and the poor afterthought that is their developer documentation, the only way we can guarantee this is with robust automated testing for every inch of the codebase.
Adherence to WPGraphQL best practices.
Headless WordPress is still a relatively new space, and the ecosystem around WPGraphQL is still maturing. To ensure long-term compatibility and encourage developer contributions, we need to make sure our plugin is doing things the accepted
WPGraphQL
way, instead of employing hacky filter overrides that are only guaranteed to work in the short term.⚠ Breaking Changes
To reach v1.0 we will need to make numerous breaking changes to the plugin. We will do our best to group multiple changes together in a single release, to make it easier on developers.
Please note that until we hit v1.0, we're using a modified version of SemVer, where
v0.[ X ]
releases may contain breaking changes (to either the PHP or the GraphQL schema), butv0.X.[ x ]
releases never will.v0.X.x.[ x ]
releases are reserved for addressing issue with the previous release only.🗺 Roadmap
The text was updated successfully, but these errors were encountered: