Skip to content

Name conflict with consolidated files #200

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

Open
alvarosabu opened this issue May 21, 2025 · 1 comment · May be fixed by #217
Open

Name conflict with consolidated files #200

alvarosabu opened this issue May 21, 2025 · 1 comment · May be fixed by #217
Assignees
Labels
p2-edge-case [Priority] Bugs with workarounds or limited impact. v4
Milestone

Comments

@alvarosabu
Copy link
Contributor

alvarosabu commented May 21, 2025

Current behavior:

When pulling components via storyblok components pull --separate-files if a user has components in their space called tags, groups, components they will collide with the system consolidated files

Expected behavior:
There is no naming collision

Steps to reproduce:
Described above

Proposed solution

Move consolidated files to a different folder .storyblok/components/xxxxx/consolidated

@alvarosabu alvarosabu added this to the v4 milestone May 21, 2025
@alvarosabu alvarosabu self-assigned this May 21, 2025
@alvarosabu alvarosabu added the p2-edge-case [Priority] Bugs with workarounds or limited impact. label May 21, 2025
@alvarosabu
Copy link
Contributor Author

cc @angelikatyborska

@alvarosabu alvarosabu added the v4 label May 23, 2025
@alvarosabu alvarosabu linked a pull request Jun 3, 2025 that will close this issue
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
p2-edge-case [Priority] Bugs with workarounds or limited impact. v4
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant