Skip to content

Add support to configure Parser #69

@clinejj

Description

@clinejj

This is stemming from an issue running erb-lint on files with AlpineJS syntax (Shopify/erb_lint#221), but it would be nice to add support to configure the parser to use some of the same configuration that better-html supports (in this case the partial_attribute_name_pattern would correct this). For example, being able to set config.partial_attribute_name_pattern = /\A[a-zA-Z0-9\-\:\@\.]+\z/ would allow for the following snippet to parse correctly:

<nav x-data="{ open: false }" @keydown.window.escape="open = false" class="bg-white border-b"></nav>

It looks like this might be a bit tricky given the underlying issue comes from the underlying html_tokenizer library.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    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