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), but v0.X.[ x ] releases never will. v0.X.x.[ x ] releases are reserved for addressing issue with the previous release only.

🗺 Roadmap

• Overview
• Planned Releases