Skip to content

/polymer

Loading…

New issue

custom-style should generate a better error when its `include` is not found #2356

Closed
sorvell opened this Issue · 0 comments

Labels

p1

Milestone

No milestone

Assignee

@sorvell sorvell

1 participant

@sorvell
@sorvell
Owner
sorvell commented

At the moment, this generates an arcane error. Instead, it should warn that the include name cannot be found.

@sorvell sorvell added the p1 label
@sorvell sorvell self-assigned this
@sorvell sorvell referenced this issue from a commit
@sorvell sorvell Fixes #2356: issue a warning and don't throw an exception when a styl… … 
…e include cannot be found.

Fixes #2357: include data now comes before any textContent in a style element.
 a16ada1
@sorvell sorvell referenced this issue
Merged

Fixes #2356, #2357 #2375

@frankiefu frankiefu closed this in #2375
@MartinMoizard MartinMoizard referenced this issue from a commit in MartinMoizard/polymer
@sorvell sorvell Fixes #2356: issue a warning and don't throw an exception when a styl… … 
…e include cannot be found.

Fixes #2357: include data now comes before any textContent in a style element.
 6365cf6
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.