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

Roadmap for next version #27

Closed
6 tasks
cometkim opened this issue Feb 16, 2020 · 4 comments
Closed
6 tasks

Roadmap for next version #27

cometkim opened this issue Feb 16, 2020 · 4 comments
Assignees

Comments

@cometkim
Copy link
Owner

cometkim commented Feb 16, 2020

@cometkim cometkim self-assigned this Feb 16, 2020
@cometkim cometkim pinned this issue Feb 16, 2020
@cometkim cometkim changed the title Roadmap for next release (2.0 maybe) Roadmap for next release Feb 16, 2020
@cometkim cometkim changed the title Roadmap for next release Roadmap for next version Feb 18, 2020
@cometkim
Copy link
Owner Author

Have to consider about #36

@cometkim
Copy link
Owner Author

cometkim commented May 2, 2020

Contributing to the core is the correct way than providing 3rd type definitions since GatsbyJS started to use TypeScript. And I have to reconsider internal type definitions and utility types to depend on the core.

@cometkim
Copy link
Owner Author

cometkim commented May 2, 2020

According to the guideline:

Lastly and most imporantly, we want to have simple types whenever possible. Primarily we should avoid Generics. Generic code can be highly reusable, but that can also come with the greater chance of breaking things. Code should be simple when possible. DRY is not always best.

Gatsby avoids type inference, and it's quite reasonable for that size of codebase.

However, we can still provide utilities for plugin/theme authors who want improved type inference. Perhaps it will be in a separate project.

@cometkim
Copy link
Owner Author

Move discussions here to #174

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

No branches or pull requests

1 participant