Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Appearance settings

URL parsing differs from other native functions #34

Copy link
Copy link
Open
#84
Open
URL parsing differs from other native functions#34
#84
Copy link
@tomrav

Description

@tomrav
tomrav
opened on Dec 28, 2017
Issue body actions

We're using the value-parser in our Stylable project, and I'm encountering a use-case that feels inconsistent with the rest of the native functions.

By parsing whatever value resides inside a url as a single parameter (and not a complex AST), I am unable to iterate over the nested children (in my case, custom functions that will resolve to a url).

Example:
Source

.some-class {
    background: url(print(some-static-url));
}

Resolved target

"[
    {
        "type": "function",
        "sourceIndex": 0,
        "value": "url",
        "before": "",
        "nodes": [
            {
                "type": "word",
                "sourceIndex": 4,
                "value": "print(some-static-url"
            }
        ],
        "after": ""
    },
    {
        "type": "word",
        "sourceIndex": 26,
        "value": ")"
    }
]"
Reactions are currently unavailable

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions
      Morty Proxy This is a proxified and sanitized view of the page, visit original site.