Skip to content
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: add ability to use default export in .hermione.conf file #862

Merged
merged 1 commit into from
Mar 12, 2024

Conversation

KuznetsovRoman
Copy link
Member

What is done

  • add ability to use export default in .hermione.conf.(j|t)s file. At the moment .ts config has to be export =

@KuznetsovRoman KuznetsovRoman force-pushed the HERMIONE-1086.default_config_export branch from 5664e86 to 4dd05d8 Compare March 7, 2024 11:22
@@ -15,7 +15,10 @@ export class Config {

static read(configPath: string): unknown {
try {
return require(path.resolve(process.cwd(), configPath));
// eslint-disable-next-line @typescript-eslint/no-var-requires
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

а как оно раньше работало без этого коммента?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

На return require eslint не ругался. А тут, видимо, из-за того, что появилось название, начал.

@KuznetsovRoman KuznetsovRoman force-pushed the HERMIONE-1086.default_config_export branch from 4dd05d8 to b4e1d6c Compare March 12, 2024 10:13
@KuznetsovRoman KuznetsovRoman merged commit 206526a into master Mar 12, 2024
2 checks passed
@KuznetsovRoman KuznetsovRoman deleted the HERMIONE-1086.default_config_export branch March 12, 2024 11:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants