classTemplate doesn't work as expected in release 1.2.0 about scuri

[gparlakov]

Hi, @danjour. I'll look into it ASAP. In the meantime, can you try a clean install (as I've changed the layout of the whole package thereight be some code mixing)?

…

On Wed, Nov 24, 2021, 16:55 danjor ***@***.***> wrote: Hello, I just upgraded from version 1.2.0-rc-custom-update-2 to 1.2.0, and it seems that at least the create spec file using classTemplate param is broken. Indeed, running the schematic simply copy de template file in the TS file folder, without replacing the content and without renaming it. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#137>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA2SEV4HWVWEOEXYIZKLM43UNT4HNANCNFSM5IWI2MCQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[gparlakov]

I can't seem to reproduce.

I seem to remember something similar happening if the template name did not end in .template or was using some invalid parameters/function calls....

Make sure the template ends in .template and is valid - use some of the (examples)[https://gist.github.com/gparlakov/f299011829e229c9d37cf0cb38506d97]

[gparlakov]

@danjor here's a place online where we can try to reproduce your issue and fix it https://stackblitz.com/edit/scuri-1-2-0-issue-134?file=example.md

Try and reproduce it there and get back to me. (see example.md file with examples of create and update commands)

[danjor]

Hi @gparlakov
Thanks for your replies again :)

Effectively, even if you previously talked about this, I missed that point about some changes that have been done for the naming of custom template in version 1.2.0

My custom template was named spec.tmpl.
So by renaming it with specFileName.template that effectively work as expected.
So there is no issue in fact.