Tagged: angular template, i18n, warnings
- This topic has 6 replies, 6 voices, and was last updated 7 years, 10 months ago by
support-swapna.
-
AuthorPosts
-
BrianParticipantThe Angular to template validator shows warnings for unknown attributes such as aria-*, data-*, and role. Under Window > Preferences > Web > HTML Files > Validation I have selected Ignore specified attribute names in validation and provided the list of patterns “aria-*,data-*,role”. I can not find any settings under Window > Preferences > Webclipse to do the same for Angular 2 validation. Is there a way to ignore these attributes in Angular 2 templates?
Attachments:
You must be logged in to view attached files.December 19, 2016 at 5:18 am #506208
support-swapnaModeratorBrian,
Currently, there is no way to suppress the warnings for unknown attributes during Angular2 template validation.
I have raised an enhancement request for the same and the dev team is looking into it.
We will keep you posted when the fix is out.Apologies for inconvenience caused. Thank you for raising it.
–Swapna
MyEclipse SupportJune 8, 2017 at 2:50 pm #526038
PaulParticipantI was wondering if there was an update to this issue?
I’m using angular 4 with bootsrap markup.
I’m getting Unknown attribute for
aria-controls
aria-hidden
role = (group, button)June 9, 2017 at 2:50 am #526100
support-piotrParticipantHi Paul,
Thanks for querying about this issue. With the latest release we’ve significantly improved validation of attributes provided by angular directives and we are now moving on to improving other validation aspects. As far as I can see,
aria-*
,data-*
androle
are valid HTML 5 attributes and should be treated as such. This will be fixed in the next release – CI 7.June 27, 2017 at 2:01 pm #528335
Brian FernandesModeratorPaul,
We will be releasing CI 7 in the next couple of days with this fix. Prior to that, we have released the fix on prerelease stream – so if you would like to test it, and provide feedback before the final release, please see this article for instructions.
Thanks!
July 20, 2017 at 8:44 am #531199
RaulParticipantHi Brian,
Updating to CI 7 has worked for me, but there is still a similar problem when dealing with Angular i18n: attributes like
i18n
ori18n-xxxx
are marked as warnings.See https://angular.io/guide/i18n for details about these attributes
This is an important issue to fix, since all my templates include these attributes.
Thanks in advance.
August 2, 2017 at 9:07 am #532621
support-swapnaModeratorRaul,
Apologies for missing your post. I could replicate the problem with i18n attributes marked as warnings at my end. I have filed a bug for the dev team to fix it. We will keep you posted when the fix is out.
Sorry for inconvenience caused.
–Swapna
MyEclipse Support -
AuthorPosts