We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Is your feature request related to a problem? Please describe. When using custom & info we'd like to supply our own typing. However they sits in a type alias instead of an interface so can cannot using type augmentation ( as state here https://www.typescriptlang.org/docs/handbook/2/everyday-types.html#differences-between-type-aliases-and-interfaces )
custom
info
Describe the solution you'd like Change type to interface for UserComponentConfig & NodeData & Node.
type
interface
UserComponentConfig
NodeData
Node
The text was updated successfully, but these errors were encountered:
Good suggestion, care to submit a PR?
Sorry, something went wrong.
Sure but not at the moment. Still in some projects and feeling out of stamina.
Something that can also be fixed is the lack of documentation of info.
And I gotta say the API of craft.js is minimal and of good taste. Enjoying every minute playing with it.
No branches or pull requests
Is your feature request related to a problem? Please describe.
When using
custom
&info
we'd like to supply our own typing. However they sits in a type alias instead of an interface so can cannot using type augmentation ( as state here https://www.typescriptlang.org/docs/handbook/2/everyday-types.html#differences-between-type-aliases-and-interfaces )Describe the solution you'd like
Change
type
tointerface
forUserComponentConfig
&NodeData
&Node
.The text was updated successfully, but these errors were encountered: