Skip to main content

And, Or, Not Operators in Component Boolean Properties

  • November 19, 2022
  • 1 reply
  • 707 views

Ali_Ghane

For me, there have been so many times when I felt the need to define an inner layer’s boolean property as opposite to another one. This happens mostly in design systems where there are a lot of inner layers in a component and sometimes, some of these components shouldn’t be visible when another is. For example, in a menu, there are some options for the items in the list like Avatars and Icons; an icon [in some systems] shouldn’t be visible when there’s an avatar. So I feel the need to define it’s property as “!Avatar && Icon” such as we see in so programming languages.

This topic has been closed for replies.

1 reply

  • 0 replies
  • February 17, 2023

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings