Skip to content
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

IMPORTANT: react-apollo-form full rewrite on-going #31

Closed
charlypoly opened this issue Jan 20, 2019 · 9 comments
Closed

IMPORTANT: react-apollo-form full rewrite on-going #31

charlypoly opened this issue Jan 20, 2019 · 9 comments
Assignees
Labels
enhancement New feature or request

Comments

@charlypoly
Copy link
Owner

Regarding the current state of the library and the growing demand on it, the react-apollo-form is currently under a "re-design" phase.

This may imply some upcoming breaking changes needed to stabilise the library.

We will keep you updated on this ticket.

@charlypoly charlypoly added the enhancement New feature or request label Jan 20, 2019
@charlypoly charlypoly self-assigned this Jan 20, 2019
@charlypoly charlypoly pinned this issue Jan 20, 2019
@snirp
Copy link

snirp commented Feb 18, 2019

Any updates on the current status?

@charlypoly
Copy link
Owner Author

charlypoly commented Feb 19, 2019

Hi @snirp !
Thanks for your interest!

Yes there is, here is the timeline for the "redesign" and rewrite of react-apollo-form that will be called formidable-forms:

  • End of February: Design phase finished 📝
  • End of March: Implementation phase finished 👨‍💻
  • April: First release + building some community materials (code-sandbox, doc site, ...) 🚢
  • April: Support for 2 famous UI-kit (ex: Semantic UI and Material UI) 💅

@charlypoly charlypoly changed the title IMPORTANT: react-apollo-form is currently on re-design phase IMPORTANT: react-apollo-form full rewrite on-going Feb 19, 2019
@lukasluecke
Copy link
Contributor

@wittydeveloper Thanks for the update and your work on redesigning this library! I just implemented the current version in a project anyway, with some minor changes - but I'll gladly try and use the new one once it's available 👍

Will there still be a "dependency" on the apollo codegen in the new version, or will you get all the required information directly?

@charlypoly
Copy link
Owner Author

Hi @lukasluecke,

Thanks for your support. 🙇

The rewrite will also benefit of a renaming of the library: Frontier forms.
The idea of the rewrite is to separate the library into many meaningful pieces in order to make it more powerful, this include:

  • support many flavours: React, React Native, Vue.js and Angular
  • support for many data schema: GraphQL and Swagger
  • also, ui-kits packages for: Material UI, Bootstrap, Semantic UI

Regarding the GraphQL part, we will propose 2 ways to use it:

  • runtime introspection using ApolloClient (better for development mode)
  • static generation using apollo-codegen (more suitable for production)

the frontier-forms-graphql will have a peerDependencies on apollo (client + codegen).

Does this answer your question?

@charlypoly
Copy link
Owner Author

For all question regarding future Migration from react-apollo-form to frontier-forms, please give a look at #33.

@lukasluecke
Copy link
Contributor

@wittydeveloper

Thank you for your detailed reply. Yes, that answers my question 🙂

And the reason I asked about the apollo codegen is that I am using graphql-code-generator for my codegen needs (generates "nicer" types in my experience, and also more than the apollo codegen, e.g. Hooks for queries and mutations - react-apollo-hooks), and to use their JSON introspection result with your library I had to modify the parsing (the only difference is, that it's not nested under a data key). Maybe you can keep that in mind, and make it easy to customize this part 😉

@EricsG95
Copy link

EricsG95 commented Apr 15, 2019

Hi @lukasluecke,

Thanks for your support. 🙇

The rewrite will also benefit of a renaming of the library: Frontier forms.
The idea of the rewrite is to separate the library into many meaningful pieces in order to make it more powerful, this include:

  • support many flavours: React, React Native, Vue.js and Angular
  • support for many data schema: GraphQL and Swagger
  • also, ui-kits packages for: Material UI, Bootstrap, Semantic UI

Regarding the GraphQL part, we will propose 2 ways to use it:

  • runtime introspection using ApolloClient (better for development mode)
  • static generation using apollo-codegen (more suitable for production)

the frontier-forms-graphql will have a peerDependencies on apollo (client + codegen).

Does this answer your question?

@wittydeveloper wow I will be totally looking forward for the full support with Angular in the future. However what is the current library state with Angular itself?

@charlypoly
Copy link
Owner Author

Hi everybody,

The development of <Frontier /> is now finished for the first 0.1.0 RC: https://github.com/frontier-forms/frontier-forms

Please know that I'll work on a migration or compatibility with react-apollo-form in the upcoming weeks.
This migration part will be the subject of another ticket.

Feel free to leave comments on https://github.com/frontier-forms/frontier-forms/issues.

@charlypoly
Copy link
Owner Author

Hi @EricsG95,

For now Frontier only support React.
I'll soon start to look for contributors for the Angular support. 👀

Stay tuned on https://github.com/frontier-forms/frontier-forms

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants