Skip to content

Fix misleading wording for list value escaping (issue #4330) #628

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
N-Yashwitha wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Fix misleading wording for list value escaping (issue #4330) #628

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion content/features/mixins-parametric.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,7 @@ Parameters are currently either *semicolon* or *comma* separated.

Originally, parameters were only separated by commas, but the semi-colon was later added to support passing comma-separated list values to single arguments.

Note: As of Less 4.0, you can wrap a list value using a paren escape [`~()`], e.g. `.name(@param1: ~(red, blue))`. This is similar to the quote escape syntax: `~"quote"`. This may make semi-colon separators un-necessary in your code-base.
Note: As of Less 4.0, you can escape a list value by using a tilde with parentheses ~(), e.g. .name(@param1: ~(red, blue)).

Examples:

Expand Down