-
-
Notifications
You must be signed in to change notification settings - Fork 33.7k
Syntax suggestion when passing props to components #11103
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
Comments
Hello, thank you for taking time filling this issue! However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!). I hope to see your helper-created issue very soon! |
Duplicate of #5835 |
Hello @posva. I can imagine how busy you probably were, so I have thank you for the attention. You marked my issue as a duplicate of #5835. They are really similiar indeed, but there are a few difference. Let's exam them. First, I'm proposing that Moreover, I also suggested that Please, I would appreciate it if you reconsider my question, and remove the Closed tag |
Please check the discussions, the arguments provided apply for both of your suggestions |
I checked the discussion and I can't see where the arguments apply to my suggestions. Could you clarify that for me, please? |
Hello. I'm still not convinced that the arguments provided apply for my suggestions since they are different. For example, the workaround proposed doesn't work with methods and my proposal for |
Hello, I'd like to suggest the following syntax that you may add to future releases.
Could be equivalent to
That would make code much cleaner when we have to pass multiple props to a child component and those props have the same name as the variables in the parent component. The same thing can be said about events.
I hope you take this into consideration and that my suggestion will help you improve VUE.
The text was updated successfully, but these errors were encountered: