Skip to content
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.

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

Add AMP validation features to support literal attribute value, e.g []. #51

Merged
merged 1 commit into from
Nov 10, 2020
Merged

Add AMP validation features to support literal attribute value, e.g []. #51

merged 1 commit into from
Nov 10, 2020

Conversation

nhant01
Copy link
Contributor

@nhant01 nhant01 commented Nov 10, 2020

  1. When inspecting the attributes for p, the "[text]" attribute is returned as "text", when these are distinct values. We are requesting a change or some feature that can return the literal value of the attribute. This is necessary for AMP validation.

  2. At the moment, tagchowder is sanitizing Unicode characters by replacing with "_". For example, a tag that looks like,
    'html ⚡4email' would be returned at the handler level as, 'html _4email'

<p {{text}}="cart.p1_qty" class="qty_num">1</p>
<p {[text]}="cart.p1_qty" class="qty_num">1</p>

<!--sanitize, all should return text -->
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you fix this one line

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

Copy link
Contributor

@fansu fansu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks ok to me

@fansu
Copy link
Contributor

fansu commented Nov 10, 2020

looks good.

@lafa lafa merged commit 11925a4 into yahoo:master Nov 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants