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

I trusted vscode's automagic use of '@/common' for the import, and clearly I shouldn't have #176

Merged
merged 1 commit into from
Jul 7, 2022

Conversation

SvenDowideit
Copy link
Member

@SvenDowideit SvenDowideit commented Jul 7, 2022

Signed-off-by: Sven Dowideit SvenDowideit@home.org.au

…early I shouldn't have

Signed-off-by: Sven Dowideit <SvenDowideit@home.org.au>
@SvenDowideit
Copy link
Member Author

fix main :(

@SvenDowideit SvenDowideit changed the title I trusted vscode's automagic use of '@/common' for the import, and cl… I trusted vscode's automagic use of '@/common' for the import, and clearly I shouldn't have Jul 7, 2022
@SvenDowideit SvenDowideit merged commit a4a3ffa into main Jul 7, 2022
@SvenDowideit SvenDowideit deleted the fix-import-paths-for-149 branch July 7, 2022 08:07
@nathanleclaire
Copy link
Contributor

nathanleclaire commented Jul 7, 2022

Yea there are a bunch of these around. My VScode complains about them. I'm considering modifying them all in one fell swoop

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