You take extra care to make this option documented and very visible everywhere. A lazy guy posts an agressive 1 star review about your tool because he thinks he cannot switch back. You reply it is absolutely possible. He does not care and leaves his negative review. You are welcome. 🙃

but actually you are left alone despite being the author of a tool with 1,5 million installations. You do a tedious work on your free time and for free to align to the change. You do extra work to allow users to revert to the previous behavior in one click.

Strict enabled by default, finally! 🎉

Unrelated, but for the fun: the npm website login page is amazing, the store blind closing when you enter your password so the animal (not sure what it is?) cannot see it, it is genius.

...and add the "()" yourself in the template file name as showed in my previous message. It implies you will have to create 2 schematics (one for "()" and one for "[]"), but it feels like a better design choice, as the details of your templates will probably be different in these 2 scenarios.

{{name}} is the raw user input, and all helpers ({{className}}, {{fileName}}...) are derived from that. So if you expect the user to type "(blog)", it is normal that {{name}} results in "(blog)". I would suggest to reverse the logic and just to expect "blog" from the user...

So {{fileName}} is an helper for the standard Angular naming convention. As you want a custom naming, just use {{name}}. For example, for your template file name: ({{name}}).ts.hbs and you are good to go. Do not forget to update the mainFile property in the schematic.json accordingly.

For special characters, I did not designed the system with that kind of filenames in mind, as it is not classic / standard Angular. But it should be achievable, let me check and I will come back to you with an example.

pathsWithPredefinedSchematic is very simple: you associate a schematic to a path so it is preselected when you right click inside this path. Full documentation and exemples inside VS Code or here: github.com/cyrilletuzi/...

There are a lot of options, but for most cases you do not need most of them. All the documentation is directly inside VS Code in the "walkthrough" feature, and also duplicated here: github.com/cyrilletuzi/... But if you still need help I can assist you further for sure.

For many reasons, the VS Code extension does not rely on the Angular CLI, it has its own generation system using native VS Code APIs, and so it also has its own custom schematics system/format (simpler, as it is purely declarative: just a template and a config file).

Hi, can you explain your use case and/or what you want to achieve exactly? I am not familiar with Analog and the documentation you linked is not very helpful to understand what feels "wrong" for you.