naz

This issue is a good example of why migrating to AST-based rules for author-related errors like [done here](https://github.com/TryGhost/gscan/commit/377e46dd867d2865f0ecd26e76ddc532ca6faea5) is a good idea.

@kirrg001 after investigating this bug and looking into how gscan handles checks internally have following thoughts: `GS001-DEPR-AUTH*` [set of rules](https://github.com/TryGhost/gscan/blob/ab44dc3/lib/specs/latest.js#L80-L213 ): (except GS001-DEPR-AUTH-MAIL) is obsolete as of Content API introduction...

@kevinansfield yes, having the context narrowed down to post/page would be the best option. In this case, we could set this bug to be an example use-case that should be...

Hi @stcherenkov! This is a `gscan` issue and after trying to activate some themes locally haven't found any issues with such naming. It's probably up for discussion if we should...

@kevinansfield my understanding is it's more about detecting usage of nested tags. In this situation it would be de detection of the following situation: ```handlebars {{#next_post}} {{^prev_post}} no prev post...

Think we can introduce both rules as they would be quite helpful. > 1. a rule that detects nested async helpers (are we sure nested async helpers will always fail?)...

The `import '@axiomhq/pino'` fix worked for my case where I use Pino with NestJS running on Vercel environment

We are facing similar issue in [Ghost's Zapier integration](https://github.com/TryGhost/Zapier). The value for `boolean` [used to be a](https://github.com/TryGhost/Zapier/commit/caa1773f11fa9dc1cba6c8fc402eaba7ee3b93e9) **string** `'0'`/`1` values. It has been changed to **boolean** `true`/`false` values without clear...