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
copy functional components from the times react knew its place
Implement pure functional components
functional components will receive the global context + inline attributes, but will have no state of its own
discussion: force components to be named functions for the sake of debug sanity
The text was updated successfully, but these errors were encountered:
#34 Adds support to pure components with the 3 following syntaxes:
const AnonComponent = function(context) { return ( <div data-anon={context.params.works} id={context.id} /> ) } function NamedComponent(context) { return ( <div data-named={context.params.works} id={context.id} /> ) } const ArrowComponent = (context) => { return ( <div data-arrow={context.params.works} id={context.id} /> ) }
Functional components are pure and the context is readonly
Sorry, something went wrong.
pure functions now receive a proxy so bind is still possible while remaining pure:
export const ArrowComponent = (context) => { return ( <input data-string={context.string} bind={context.string} /> ) }
Mortaro
No branches or pull requests
copy functional components from the times react knew its placeImplement pure functional components
functional components will receive the global context + inline attributes, but will have no state of its own
discussion: force components to be named functions for the sake of debug sanity
The text was updated successfully, but these errors were encountered: