Skip to main content
n_zrk
February 28, 2024
Question

'No' / 'Yes' variants, after being automatically converted to boolean, are still treated as string, stopping boolean variables binded to an instance from working

  • February 28, 2024
  • 12 replies
  • 2279 views

I couldn’t find a bug report, so just in case I’m posting my own.

If we create a component with ‘No’ / ‘Yes’ variants (which Figma transform automagically into boolean) and we bind variable to that it’s not working. Since it shows as a boolean we can only bind boolean variable, but when we do that the variable name is crossed out and it’s not working.

I suspect it happens because Figma still treats that variant as a ‘string’. If I change variant names to something else (so it’s not transformed into boolean) and I use string variable it’s working just fine.

    This topic has been closed for replies.

    12 replies

    Show previous replies
    Chene_He
    Chene_He
    New Member
    July 31, 2025

    For anyone encountering this issue. Here is a workaround:
    You can’t select a string variable but you can create one by clicking on this plus

    grafik


    Then you can name and create the variable. After that change the text to the matching Component Text.

     

    I’m honestly very suprised that this bug still exists? Why am I not able to bind booleans to Component Names detected as a boolean?

     

     

    Hi Paul,
     

    I've tried to create a new variable, it still happening. The local vaviables auto-generates with "false" "ture" but the variants only become boolean when I named it as Yes NO, or On off. which doesnt match the local vaviables. 

     

    Antonio_Augusto_Furtado_de_Far
    Antonio_Augusto_Furtado_de_Far
    New Member
    August 28, 2025

    I’m having the same problem. It’s a shame that it’s happening for more than 1 year already and nothing has been done.

    Terms & ConditionsAccessibility statement