-
Updated
Sep 25, 2021 - JavaScript
best-practices
Here are 1,237 public repositories matching this topic...
-
Updated
Oct 3, 2021 - JavaScript
-
Updated
Oct 1, 2021 - JavaScript
-
Updated
Oct 1, 2021 - JavaScript
-
Updated
Oct 1, 2021
-
Updated
Oct 4, 2021 - Python
-
Updated
Oct 1, 2021 - Shell
-
Updated
Oct 4, 2021 - HTML
-
Updated
Mar 1, 2021
-
Updated
May 12, 2020
-
Updated
Oct 2, 2021 - C#
-
Updated
Aug 14, 2021
-
Updated
Sep 15, 2021
-
Updated
Oct 4, 2021 - HTML
-
Updated
Aug 26, 2021 - HTML
-
Updated
Sep 29, 2021 - JavaScript
-
Updated
Oct 3, 2021 - JavaScript
-
Updated
Sep 7, 2021 - Python
-
Updated
Aug 9, 2021 - Kotlin
-
Updated
Jan 9, 2019
-
Updated
Aug 26, 2021
-
Updated
May 24, 2021 - TypeScript
-
Updated
Sep 13, 2021 - C#
-
Updated
Oct 4, 2021 - TypeScript
Merge /Testing_for_Vertical_Bypassing_Authorization_Schema_WSTG-AUTHZ-00X.md
into 4-Web_Application_Security_Testing/05-Authorization_Testing/03-Testing_for_Privilege_Escalation.md
-
Updated
Dec 23, 2020 - Python
🐞 Bug report
Description
In vscode, whenever I set the "extends"
property in my tsconfig.json
file, webhint gives the following error message:
Unexpected token } in JSON at position 705 (typescript-config/is-valid)
Details
Web Packaging "comes in several layers":
-
Bundled HTTP Exchanges (Web Bundles):
https://datatracker.ietf.org/doc/html/draft-ietf-wpack-bundled-responses.wbn
file extension =application/webbundle
-
Signed HTTP Exchanges:
https://tools.ietf.org/html/draft-yasskin-http-origin-signed-responses.sxg
file extension = `application/signe
Improve this page
Add a description, image, and links to the best-practices topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the best-practices topic, visit your repo's landing page and select "manage topics."
Feature request summary
I could find some reference to the use of locale in the docs, but not which locale were supported? Can I get the interface in Spanish? The reports in Thai? What parameters are supported? Is there a list of supported strings to translate?
What is the motivation or use case for changing this?
Non-English users generally are not prioritizing accessibility https:/