Missing template to render

[gymgnopf]

Hey thank you for your awesome work.

After updating to version 1.4, I get the error 'Missing template to render', when I click on 'Insert all PHP Getter & Setter'.
I dont use custom templates, but I checked the folder '%APPDATA%\Code\User\phpGettersSetters' and didn't see any template files.

'Insert PHP Getter & Setter' works just fine.

Thank you for looking at it.

[cvergne]

Hi,

That is strange because all commands are using the same render method.
I neither have any template file and it's working fine.

Did you try to restart VSCode ?
The bug is on any file ? Could you give an example ?

[cvergne]

Also could you send a screenshot of your extension settings ? (you can right click on the extension in the sidebar then "Extension Settings")

[gymgnopf]

Hi, thank you for your answer.
I did restart VSCode but the problem is still there.

.

I hope this is helpful.

[cvergne]

Everything seems normal at this point.
Do you have phpGettersSetters.templatesDir in settings.json? (if you click on "Edit in settings.json")

[gymgnopf]

No, there was no entry.

[alcalyn]

Same here, works for "Insert PHP getter", "Insert PHP setter", "Insert PHP getter & setter", but does not works for "Insert ALL PHP getter & setter".

I tried to define a phpGettersSetters.templatesDir with my custom getter and setter templates, but I get same result.

[cvergne]

@alcalyn Do you have an example of PHP code not working on your side please ? :)

[alcalyn]

Sure, I can reproduce it with a very simple class:

<?php

class Hello
{
    private int $number;

    private DateTime $date;
}

Working: Insert getter, setter, getter & setter for both individual properties.

Not working: Insert ALL getter and setter, I get phpGettersSetters error: Missing template to render.

About my vscode:

Version: 1.64.0
Commit: 5554b12acf27056905806867f251c859323ff7e9
Date: 2022-02-04T06:27:19.879Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Linux x64 5.13.0-28-generic

[cvergne]

So, should be fixed on v1.6.0. Thanks :)