feat: Nuxt Layer Support for autoImportPath - #272
Open
larsalbrecht wants to merge 2 commits into
Open
Conversation
* Collect all importPaths from layers * Check for non-layers * Call addComponentsDir for all found directories
larsalbrecht
force-pushed
the
feature/nuxt-layer-support-for-auto-import-path
branch
from
May 22, 2024 10:44
eb1a02b to
c6ccc3d
Compare
larsalbrecht
changed the title
|
Can someone help me with the type issue? How can I make the linter understand that the SVGO config is also used there and that is why the key exists? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why?
Current status:
If you use nuxt-layers and have an autoImportPath in the layer, for example, this will be overwritten if you also use one in the app.
New status:
Each layer is searched for autoImportPath and all are added.