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

[next] fix: Adjust tsconfig and eslintrc for tests #5569

Merged
merged 1 commit into from
May 11, 2024
Merged

Conversation

susnux
Copy link
Contributor

@susnux susnux commented May 8, 2024

☑️ Resolves

  • Fixes rootdir in invalid place in tsconfig.
  • Fixes wrong location of eslintrc

🏁 Checklist

  • ⛑️ Tests are included or are not applicable
  • 📘 Component documentation has been extended, updated or is not applicable

* Fixes `rootdir` in invalid place in tsconfig.
* Fixes wrong location of eslintrc

Signed-off-by: Ferdinand Thiessen <[email protected]>
@susnux susnux added bug Something isn't working 3. to review Waiting for reviews vue 3 Related to the vue 3 migration labels May 8, 2024
@susnux susnux added this to the 9.0.0-alpha.3 milestone May 8, 2024
@@ -12,11 +12,13 @@
"strict": true,
"noImplicitAny": false,
"outDir": "./dist",
"rootDir": "./src",
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe make it just the root to keep structure?

Suggested change
"rootDir": "./src",
"rootDir": ".",

Copy link
Contributor Author

@susnux susnux May 10, 2024

Choose a reason for hiding this comment

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

The the output will be dist/src/... instead of dist/...
And would also include files in the output that are only for development.

So setting root to our sources only.

@ShGKme ShGKme changed the title fix: Adjust tsconfig and eslintrc for tests [next] fix: Adjust tsconfig and eslintrc for tests May 10, 2024
Copy link
Contributor

@ShGKme ShGKme left a comment

Choose a reason for hiding this comment

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

Is it needed only for next?

@susnux
Copy link
Contributor Author

susnux commented May 10, 2024

Is it needed only for next?

Yes only on next this is an issue

@susnux susnux merged commit 2b34934 into next May 11, 2024
18 checks passed
@susnux susnux deleted the fix/next-config branch May 11, 2024 10:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3. to review Waiting for reviews bug Something isn't working vue 3 Related to the vue 3 migration
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants