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

Explain why we need YAGrid #20

Open
sebastienjust opened this issue Apr 17, 2021 · 0 comments
Open

Explain why we need YAGrid #20

sebastienjust opened this issue Apr 17, 2021 · 0 comments
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@sebastienjust
Copy link
Member

sebastienjust commented Apr 17, 2021

Explain in a few words why we needed YAGrid, including

  • need for a style-free component
  • do not depend on any other framework than react
  • strong typing system
  • plugin architecture
  • for apps with hundreds of tables that need to be industrialized
  • editing table data as a very strong feature based on type system
  • separate view from data, especially for data rendering and editing needs
  • do not always match columns to data
  • externalized data (the component does not manage the data itself)
  • not relying on components for state management
  • better error management
  • etc.
@sebastienjust sebastienjust added the documentation Improvements or additions to documentation label Apr 17, 2021
@sebastienjust sebastienjust self-assigned this Apr 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant