[email protected]

[stainge]

fix for [email protected] because of feat(core): merge all client files hooks into clientConfigFile

[ota-meshi]

Thank you for this PR.
Could you fix the eslint error? Use suppression comments for one of the warnings.

[ota-meshi]

Suggested change

// eslint-disable-next-line @typescript-eslint/naming-convention -- component

[stainge]

Thank you for this PR. Could you fix the eslint error? Use suppression comments for one of the warnings.

I have updated clientAppEnhance.ts
I'm not familiar with eslint though

[ota-meshi]

Run npm run lint to check with eslint.
Run npm run eslint-fix to fix some of the reports with eslint. This will fix the formatting issue.
If you want to know the details of the command, please look in package.json.

[ota-meshi]

If you are using VS Code, I recommend that you install the eslint extension.
https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint
You can check in real time on the editor. In addition, this repository is configured to auto-fix reports that can be auto-fixed on the file save.

[stainge]

I have updated index.ts

[ota-meshi]

Thank you!