chore: Refactor imports to use the new component paths in Vue files #2571
+103
−103
Conversation
This file contains 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
Signed-off-by: Christian Hartmann <[email protected]>
Chartman123
added
javascript
Koc
reviewed
Feb 19, 2025
| import NcContent from '@nextcloud/vue/dist/Components/NcContent.js' | ||
| import NcEmptyContent from '@nextcloud/vue/dist/Components/NcEmptyContent.js' | ||
| import NcLoadingIcon from '@nextcloud/vue/dist/Components/NcLoadingIcon.js' | ||
| import NcAppContent from '@nextcloud/vue/components/NcAppContent' |
There was a problem hiding this comment.
during my work with Nextcloud I always wondering: why can't we use components auto-import instead of writing tons of this imports?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Signed-off-by: Christian Hartmann [email protected]