Cannot rename slices without breaking slice machine - V 1.5.0

[Ali-Parandeh]

Versions

• slice-machine-ui: 1.5.0
• node: V 16.18.0

Steps to reproduce

Create a slice.
Save slice
Push Slice
Rename Slice
Save Slice
Push Slice
Create a new slice with old slice name
Save Slice
Push Slice

You will face issues.

What is expected?

You should be able to rename old slices, save them and push them. Then create new slices with old names.
For instance, I created a Services slice then realised I needed to call it ServicesCategory slice. And wanted to create another slice called Services but couldn't.

What is actually happening?

1. Duplicate Slices

2. When trying to edit one of the slices - Remove a field then save.

[eraykeskinmac]

We've been getting the same error since today morning, I think it's because of the next adapter, but I still haven't solved it since I updated the next adapter.

[comeprismic]

Hi there,

Thanks for your message. The reason why you are getting these errors is that the rename feature does not rename the id that is unique. This is a feature improvement that we know about and will have to do in the future, but this has not been prioritized yet to be transparent.

We will come back here when we re-open the topic.

Best,

Côme

[ShadowWayve]

I hit a related problem today.

Steps:

1. Created a slice (yesterday). I called it "Welcome". Pushed the changes.
2. Rename the slice using Slice Machine. New name: "PageIntro". (I did not push anything. This is purely a local change.)
3. Reverted all local git changes so I could split some stuff into separate git commits.
4. Repeated step#2 (rename slice "Welcome" to "PageIntro").

Expected result: The rename succeeds.

Actual result: Rename fails with an unexpected error. I hit F12 and looked at the console logs. They say:

An unexpected error happened while renaming “Welcome”. 
[{…}]
0
: 
{name: 'Error', message: 'Error in `@slicemachine/adapter-next` during `slice:rename` hook: dest already exists.'}
length
: 

Is there any way to clear out whatever got created behind the scenes during the initial rename? I tried clearing the browser history, and restarting the terminals. I suppose maybe I should attempt a reboot too, though I doubt that'll fix it.

I guess it's possible that the rename called server-side Prismic API and made permanent changes to the server-side repo, even though I never pushed the rename anywhere. And that's why the repo somehow remembers the change, behind the scenes?

Is there some kind of a client- or server-side cache I could clear so I can use the slice name I'd prefer?

Edit: 2 hours later, I might have figured out what was causing the error: Even though I reverted all the local git changes, I didn't manually delete the parent folder that was created for "PageIntro". So maybe that's what was causing the error. Or maybe not. In any case: I've been able to rename "Welcome" to "PageIntro".