-
|
Hi~ieedan My file structure is something like this.The migration tool works fine. But I don't want to list all files. 😂{
name: 'drawer',
add: 'when-added',
type: 'notification',
files: [
{
path: 'src/components/notification/drawer',
files: [
{
path: 'drawer-body.vue',
},
{
path: 'drawer-close.vue',
},
{
path: 'drawer-content-impl.vue',
},
{
path: 'drawer-content-swipeable.vue',
},
{
path: 'drawer-content.variants.ts',
},
{
path: 'drawer-content.vue',
},
{
path: 'drawer-footer.vue',
},
{
path: 'drawer-header.vue',
},
{
path: 'drawer-overlay.vue',
},
{
path: 'drawer-portal.vue',
},
{
path: 'drawer-root.vue',
},
{
path: 'drawer-trigger.vue',
},
{
path: 'drawer.test.ts',
role: 'test',
},
{
path: 'index.exports.ts',
},
{
path: 'index.namespaced.ts',
},
{
path: 'index.ts',
},
{
path: 'useDrawerSwipe.ts',
},
],
},
],
}Maybe add some options like |
Beta Was this translation helpful? Give feedback.
Answered by
ieedan
Dec 4, 2025
Replies: 2 comments 8 replies
-
|
In this case I would probably recommend you write your own function to collect the files for the registry. It's a slippery slope to start adding options like that. You can check out reactbits for a good example of this |
Beta Was this translation helpful? Give feedback.
1 reply
Answer selected by
BuptStEve
-
|
BTW how about resolving snapshots as test files as default? |
Beta Was this translation helpful? Give feedback.
7 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In this case I would probably recommend you write your own function to collect the files for the registry. It's a slippery slope to start adding options like that.
You can check out reactbits for a good example of this