Slice machine generates new mock data - Pull requests

[kris (Kristiyan Bogdanov)]

Hey,

I've noticed that Slice Machine generates new mock data every time I make a change to the custom type or a slice. This is all good if you are working by yourself, but when collaborating with a team, it makes the Pull Requests unnecessarily large and full of non-relevant changes. Maybe worth considering making it static until the dev chooses to change it?

[Pau]

Hello @kris, thanks for the feedback. We're aware of this behaviour, and we have an open feature request to make this change. I'll add your conversation as part of the same request.

[Phil (Phil Snow)]

Hey Kris,

You could also set git to ignore the Slice Machine file.

Is necessary commit .slicemachine folder?

@soheima.canton well I've checked with our dev team, and in fact, you don't need to commit the whole folder, all what you need is to commit is .Slicemachine/mock-config.json and the rest is regenerated every time you hit save in the UI. So basically you can add the .Slicemachine to .gitignore with an exception to that file.

Thanks.