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

When specifying the path when importing, it is now easier to specify … #1551

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

EdamAme-x
Copy link
Contributor

The method of specifying from "~/" is very straightforward. For example, using import Counter from "./islands/Counter.tsx" instead of import Counter from "~/islands/Counter.tsx". We believe that the former is less likely to lose the directory structure.

Oops, I feel like I already know this.

Anyway, this should be accepted as a memorable first directory notation...

…the path from the root directory of the project.

The method of specifying from "~/" is very straightforward. For example, using import Counter from "./islands/Counter.tsx" instead of import Counter from "~/islands/Counter.tsx". We believe that the former is less likely to lose the directory structure.

Oops, I feel like I already know this.

Anyway, this should be accepted as a memorable first directory notation...
demo/deno.json Outdated Show resolved Hide resolved
Copy link
Contributor

Choose a reason for hiding this comment

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

Can you please modify components, routes, islands, etc., to use this new import prefix?

@EdamAme-x
Copy link
Contributor Author

I see.
I am ashamed to say that I have never heard of @/ before.
I'm going to go change the import prefix for each component.

EdamAme-x and others added 2 commits August 2, 2023 00:09
Change prefix

Co-authored-by: Asher Gomez <ashersaupingomez@gmail.com>
@EdamAme-x
Copy link
Contributor Author

Oops, warn of types

@EdamAme-x
Copy link
Contributor Author

How should we deal with...

@deer
Copy link
Contributor

deer commented Aug 2, 2023

This reminds me of #471.

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.

3 participants