Set different preview layout for the builder

Maybe there is a simple way to do this but something as simple as fractal.components.set('builder.preview', '@anotherpreview'); isn’t working.

Any other way to do this?

[iKasch]

Ok, i solved it.

// Set the preview layout
if (env == 'build') {
  fractal.components.set('default.preview', '@build');
  fractal.components.set('files.preview', '@build');
  console.log('We are using the following preview layout: ' + fractal.components._config.default.preview);
} else {
  fractal.components.set('default.preview', '@preview'); 
  fractal.components.set('files.preview', '@preview');
  console.log('We are using the following preview layout: ' + fractal.components._config.default.preview);
}

The important part is fractal.components.set('files.preview', '@build'); The Docs only mention default.preview but not files.preview. I’m not sure it this is a bug or if the Docs are wrong or if i misunderstood something completely but this works for now.

✌️

[mihkeleidast]

I investigated this a bit. Working as expected in my testing.

The files.preview setting is used to look up a default preview file for a directory - e.g. if you have a preview.hbs in your src/components/collection folder, that preview file is automatically used for components in that collection. So this issue seems to happen only with some specific file structure that I haven’t been able to replicate. Essentially if you have a preview template file in a collection directory, that preview is used instead of the default preview. If anyone running into this can provide a repository with this issue present, it would be great.

Either way, I’d like to know what the usecase is for using different preview templates serving/building and if maybe this would be better solved by conditional statements in a single preview template.

Closing this again, feel free to comment if any new info pops up and I can revisit this issue.