You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I didn't specify constructor. Intuition would tell me that for a ["render"] option, that method shouldn't be emitted. It could be emitted for [] (i.e. by default), and for ["constructor", "shouldComponentUpdate"] (i.e. if explicitly specified).
Cheers - Victor
The text was updated successfully, but these errors were encountered:
Anyway, the componentMethods as you can see isn't exclusive and add extra methods to the component (and doesn't check if exist or not one method inside the list).
For now, I can propose a PR where I can change the documentation that explicit these.
And for the future, we can think which is the best behaviour for that option.
Currently, I'm working on the v2 and I can consider changing that option to accept every method to include in the components.
Thank you for your proposal and help 👍
CVarisco
changed the title
componentMethods option - unintuitive behavior
Proposal: componentMethods option - unintuitive behavior
Mar 9, 2018
Hi again!
I tried setting
"componentMethods": ["render"],
in my .ccarc.This results in the following:
I see two issues here:
render
methodconstructor
. Intuition would tell me that for a["render"]
option, that method shouldn't be emitted. It could be emitted for[]
(i.e. by default), and for["constructor", "shouldComponentUpdate"]
(i.e. if explicitly specified).Cheers - Victor
The text was updated successfully, but these errors were encountered: