Watcher does not reload filters when they are changed

[jonaslagoni]

When using the watcher and you change the filter it does recognize the change, however they are never applied.

[fmvilas]

Not sure why this is happening but, without looking at it, I'm suspecting the watcher is ignoring hidden files and the .filters directory is hidden. Actually, any file starting with a dot is treated as a hidden file.

[jonaslagoni]

Not sure why this is happening but, without looking at it, I'm suspecting the watcher is ignoring hidden files and the .filters directory is hidden. Actually, any file starting with a dot is treated as a hidden file.

The watcher is recognizing the change in the hidden file, however when it re-generates it will not use the new filter, but use a cached one (the one first loaded when the command was first run).

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴
It will be closed in 30 days if no further activity occurs. To unstale this issue, add a comment with detailed explanation.
Thank you for your contributions ❤️

[derberg]

I was able to reproduce the issue even with the current generator version where we keep templates separately and filters also separately from template files

[derberg]

after few hours of debugging I'm sure problem is here
https://github.com/asyncapi/generator/blob/master/lib/filtersRegistry.js#L39

If I read file like fs.readFileSync(filePath, 'utf8') it shows new content, but require brings initial module and not the new one.

[derberg]

after finding where the issues is, finding fix was easy
interesting read about modules cache -> https://bambielli.com/til/2017-04-30-node-require-cache/

will provide PR soon

[asyncapi-bot]

🎉 This issue has been resolved in version 0.46.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀