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

@/CivicSignalBlog - Implicit imports not working for Subpath Import Aliases #904

Open
m453h opened this issue Oct 1, 2024 · 0 comments
Open
Labels
chore A task that needs to be done (neither enhancement or bug)

Comments

@m453h
Copy link
Contributor

m453h commented Oct 1, 2024

As described in PR #902

This is a minor issue and shouldn't be a blocker, but it would be nice to address, so it’s worth exploring.

After switching to Subpath Import Aliases, we are currently required to explicitly include the filename in all our imports, even when an index.js file is present. As a result, you may encounter imports like:

import slug from "#civicsignalblog/payload/fields/slug/index";

Instead of

import slug from "#civicsignalblog/payload/fields/slug";

It would be much better if we can find a clean and reusable way to automatically resolve index.js file from our import paths.

@m453h m453h added the chore A task that needs to be done (neither enhancement or bug) label Oct 1, 2024
@m453h m453h added this to COMMONS Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore A task that needs to be done (neither enhancement or bug)
Projects
Status: No status
Development

No branches or pull requests

1 participant