Variable Naming Issues

When naming variables, there are a few cases that cause Yaak to fail to parse the values.

Numbers in Variable Names:

Putting a number at the start of a variable’s name does not work, but numbers within the name does work.

Works: numbered_1_name: https://feedback.yaak.app/help

Fails: 2_numbered_name: https://feedback.yaak.app/help numbered_2_name: https://feedback.yaak.app/help

Error: Failed to parse URL "http://${[ 2_numbered_name ]}": invalid international domain name

Dot in Variable Names:

When using a variable with a dot in its name, the variable autocomplete treats this as a nested value (which is great), but the variable fails to parse when used. The autocomplete breaking this down into dot → name seems to suggest that this is a supported use case, but it currently is not.

Fails: dot.name: https://feedback.yaak.app/help

Error: Failed to parse URL "http://${[ dot.name ]}": invalid international domain name

This also fails when inlining a variable that uses a dot in its name.

Fails:

nested.base: feedback.yaak.app

inline_full: https://${[ nested.base ]}/help

Error: Failed to parse URL "https://${[ nested.base ]}/help": invalid international domain name