Artur Balsam

@IagoAbal @mmcqd the 'issue' is still there, but I am closing this one, as it is working for me (Zero width space)

I think, that might be an explanation: https://github.com/returntocorp/semgrep/blob/3548a568b7fe4661e045237e315f048c11072209/cli/src/semgrep/autofix.py :)

Quick solution for now: I could possibly use rule, with count to be applied once, and run semgrep multiple times (non-ideal, but it worked for some usecases).

@ievans https://github.com/returntocorp/semgrep/commit/1a1c716506a968f8b461bd58ca0b14724705d431 it seems like fix was already applied without connecting with this issue. As it is fixed, I am closing it!

@ievans When it will be available for stable version?

Could we add some flexibility to the whole hydrator mechanism - with making it possible to be before (and after) each step (authentication, authorization and mutation)? For example to rule...

That's shame! `Oathkeeper` was such a nice name!