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
Hi, first of all your extension looks amazing as it is! Thank you for it.
My question is not a nitpick, but rather a curiosity. As you probably noticed, my attempt to add a note about this extension into github-script actions/github-script#507. I thought it would help other people to discover this extension, but alas that didnt work out.
In the meantime I started to use it at work and people didnt fancy custom annotations and judged it to be a tad fragile. But without annotations the extension doesn't work.
All of this got me thinking why annotation is needed in the first place? at least for the github-script action and its with.script field? this field will always be javascript. I'm not sure if it's possible for this extension to highlight this field by default as if the annotations were there?
and the second question if it is possible would you be open for this feature?
The text was updated successfully, but these errors were encountered:
Hi, first of all your extension looks amazing as it is! Thank you for it.
My question is not a nitpick, but rather a curiosity. As you probably noticed, my attempt to add a note about this extension into github-script actions/github-script#507. I thought it would help other people to discover this extension, but alas that didnt work out.
In the meantime I started to use it at work and people didnt fancy custom annotations and judged it to be a tad fragile. But without annotations the extension doesn't work.
All of this got me thinking why annotation is needed in the first place? at least for the
github-script
action and itswith.script
field? this field will always be javascript. I'm not sure if it's possible for this extension to highlight this field by default as if the annotations were there?and the second question if it is possible would you be open for this feature?
The text was updated successfully, but these errors were encountered: