I've recently created a new Next.js project to upgrade from an early version of Prismic, to use the lastest edition of the Slicemachine, and a new version of Next.js.
When building the new site, I've been leaning on the Prismic data already there, and manually creating my slices and content types in the new slicemachine locally. Then, I'm replacing the relevant parts of the JSON for the Types with the code from JSON editor so that everything is "synced" with the db.
Is this the right approach, or is there a better way to "pull" the types and slices into my new code base, so that I can ensure nothing will break when I sync everything again and/or go live with the new project?
On a related note, I didn't copy all of the content types over into the new slice machine, since some were not being used any more. Will these ever disappear because they're not in the new repo, or do they live on because they're in the db? I wasn't able to find exactly the info I need about this in the docs; this is kind of new since Types weren't ever in the old version of the slicemachine, but there they are in the new one...
thanks @Priyanka, but I'm not sure this address the question exactly. I don't want to pull from the slicemachine, as I've already reproduced everything I need. I'm wondering if I can pull the Types from the Prismic endpoint, where Types were originally created. The new slicemachine provides the ability to manage Types, whereas previously these were only defined in the Prismic db.
I'm wanting to avoid overwriting the existing Types in the Prismic endpoint since I had to create them in the new slicemachine, as I'm only rebuilding the web project, not the Prismic db endpoint.
Does that clarify? I think I'm safe as it indicates things are "synced" but I don't want to risk breaking things...