Fine-grained computed #343
Closed
vladislavarsenev
started this conversation in
General
Replies: 2 comments 2 replies
-
|
My recommendation for this case if just to ignore and let If it doesn’t generate |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
Got it. Thank you for spending time in new year eve to clarify that! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi!
Thanks for beautiful library! I'm just investigating whether I can use it on my project or not. I suppose, I'm using this library improperly and would appreciate any suggestion of best practice in my case.
Since documentation says that all business logic should be in store, I tried to move everything I could to there, but struggle with
computedfunction.I have a new card with
mapAnd I want to hide some part of site in case title is empty
I created
computedvalueBut in this case
$isPartHiddenwill be recalculated every time whatever inside $card changed. Even if I change description in it. There is a fine-grained control inuseStorewith keys, but it is used particularly in components and there is no such thing incomputed.As a workaround I can create every property as an
atominsidemap, but it seems overhead.What would be a right move according library philosophy?
Beta Was this translation helpful? Give feedback.
All reactions