because this issue will probably take literally years to resolve (it's been baried in the backlog for months now) I thought I could find a workaround and ignore the faulty files for this extension. Yet, no matter what glob I try I can't seem do it, probably because of the pattern relativity to the Workroot (#28) and the "file's" path starting with "git:/" which doesn't map to anything. I don't even know what the "real" path is:
I tried everything
I know it's technically not your bug, but I would be very grateful if you could help. Incorporating an internal filter that only allows actual existent files to be linted wouldn't harm to have anyway. Or maybe at least writable files (these .js.git things are readonly) so that new not yet saved files could be still linted.
because this issue will probably take literally years to resolve (it's been baried in the backlog for months now) I thought I could find a workaround and ignore the faulty files for this extension. Yet, no matter what glob I try I can't seem do it, probably because of the pattern relativity to the Workroot (#28) and the "file's" path starting with "git:/" which doesn't map to anything. I don't even know what the "real" path is: I tried everything
tried both with
/
and\\
.I know it's technically not your bug, but I would be very grateful if you could help. Incorporating an internal filter that only allows actual existent files to be linted wouldn't harm to have anyway. Or maybe at least writable files (these .js.git things are readonly) so that new not yet saved files could be still linted.
Thank you.