You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For .pysa files, the highlighting should look like exactly what you get in a .py file. As a start, see if we can just get a Python syntax highlighter to passably highlight the file. As a stretch goal, see if you can modify the Python syntax highlighter into treating the fully qualified function name the same as a normal unqualified function name. As a REAL stretch goal, see if you can treat DSL code in .pysa files as an embedded language and highlight it differently
taint.config files are just JSON files, so all you need to do is apply a JSON highlighter to the file.
The text was updated successfully, but these errors were encountered:
The goal here is to have the plugin turn on syntax highlighting for the two kinds of files relavent to Pysa:
taint.config
and*.pysa
files.Here are the VSCode docs on syntax highlighting.
For
.pysa
files, the highlighting should look like exactly what you get in a.py
file. As a start, see if we can just get a Python syntax highlighter to passably highlight the file. As a stretch goal, see if you can modify the Python syntax highlighter into treating the fully qualified function name the same as a normal unqualified function name. As a REAL stretch goal, see if you can treat DSL code in.pysa
files as an embedded language and highlight it differentlytaint.config
files are just JSON files, so all you need to do is apply a JSON highlighter to the file.The text was updated successfully, but these errors were encountered: