-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: use 'testplane.config.[tj]s' config name #40
Conversation
TESTPLANE_NEW_TS: "testplane.config.ts", | ||
TESTPLANE_NEW_CTS: "testplane.config.cts", | ||
TESTPLANE_NEW_JS: "testplane.config.js", | ||
TESTPLANE_NEW_CJS: "testplane.config.cjs", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Тут перечисляем список, чтобы кидать ошибку при попытке перезаписать имеющийся конфиг (проинициализировать testplane в проекте, где он уже есть):
Looks like .../my-project-dir already contains "testplane.config.ts".
Please remove old config or choose another directory.
Looks like .../my-project-dir already contains ".testplane.conf.ts".
Please remove old config or choose another directory.
@@ -12,7 +12,14 @@ describe("package", () => { | |||
}); | |||
|
|||
describe("initApp", () => { | |||
[".testplane.conf.ts", ".testplane.conf.js", ".hermione.conf.ts", ".hermione.conf.js"].forEach(configName => { | |||
[ | |||
".testplane.conf.ts", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you can get names from CONFIG_NAMES
constant instead of manually synchronizing them here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is good in source files, but i dont think it is in test files. I want small typo in CONFIG_NAMES to break these tests, so you would double-check it here
No description provided.