Replies: 1 comment 1 reply
-
I agree with this. Would you like to PR a change that does the rename and deprecates the previous name? I would like to still keep a re-export to avoid a breaking change |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This is probably a very small nitpick but I don't understand why we need the #[function_component] macro to be prefixed with "function_".
I understand the original decision for the name as this was still when struct components were quite prevalent and a clear distinction was warranted. However, with the current state of function components, I feel it would be more elegant to simply write #[component].
There is little room for confusion as the syntax between the two components is already very different. Conversely, I think it could even be clearer to beginners who wonder why the "function" part is repeated when you're already writing a function.
Furthermore, I've seen multiple other frameworks that also use only #[component].
Beta Was this translation helpful? Give feedback.
All reactions