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

Trusted Types compatibility: script for identifying violations #105747

Closed
annkamsk opened this issue Aug 31, 2020 · 1 comment · Fixed by #105748
Closed

Trusted Types compatibility: script for identifying violations #105747

annkamsk opened this issue Aug 31, 2020 · 1 comment · Fixed by #105748
Assignees
Labels
engineering VS Code - Build / issue tracking / etc. insiders-released Patch has been released in VS Code Insiders
Milestone

Comments

@annkamsk
Copy link
Contributor

As mentioned in the #103699 thread by @jrieken, there is a need for a tool that would help developers engaged in the VSCode project identify the Trusted Types violations. This can be achieved by adding tsec as a devDependency and an appropriate yarn script.

@mjbvz mjbvz assigned jrieken and unassigned mjbvz Aug 31, 2020
@jrieken jrieken added this to the September 2020 milestone Sep 1, 2020
@jrieken jrieken added the engineering VS Code - Build / issue tracking / etc. label Sep 1, 2020
@jrieken jrieken modified the milestones: September 2020, August 2020 Sep 1, 2020
jrieken added a commit that referenced this issue Sep 1, 2020
@jrieken
Copy link
Member

jrieken commented Sep 1, 2020

I have also added a task-definition so that tsec errors show in the editor itself. F1 > Run Task > tsec

Screenshot 2020-09-01 at 13 07 22

@github-actions github-actions bot locked and limited conversation to collaborators Oct 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
engineering VS Code - Build / issue tracking / etc. insiders-released Patch has been released in VS Code Insiders
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants
@jrieken @mjbvz @annkamsk and others