Use templates sent along with the request.

[Pixelatex]

Templates are compiled by an older service that we can't replace. To use fragments, we'd like to run tailor over the resulting html output before it gets sent back to the client.

So basically we'd send a call to the tailor node server that contains a stringified html.

However... it seems like tailor requires templates to be physical files in your own folders or on a server somewhere else... :/

I'd expect there to be a "template = string" option that we can pass to the request handler.

[stevoPerisic]

You can accomplish this by setting the fetchTemplate to a custom function where you retrieve the html from your legacy service. Let me know if you have any additional questions.

…

Sent from my iPhone

On Oct 3, 2019, at 9:36 AM, Pixelatex ***@***.***> wrote: Templates are compiled by an older service that we can't replace. To use fragments, we'd like to run tailor over the resulting html output before it gets sent back to the client. So basically we'd send a call to the tailor node server that contains a stringified html. However... it seems like tailor requires templates to be physical files in your own folders or on a server somewhere else... :/ I'd expect there to be a "template = string" option that we can pass to the request handler. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[stevoPerisic]

let tailor = new Tailor({
    templatesPath: __dirname + '/../templates', // in case you had any local templates
    fetchTemplate: (templatesPath, baseTemplateFn) => {
        // any logic you might have that gets returns a Promise fetching the template
    },
});

[atkinchris]

Did you solve this @Pixelatex? I'm in a similar position, using fetchTemplate to query the older service to get the HTML. However, it's not possible to pass cookies and headers from fetchTemplate to the response.

[Pixelatex]

@stevoPerisic apologies that I never responded, the fetchTemplate does work indeed
@atkinchris I have no need for passing along cookies and headers like that, I think your implementation may need tweaking to use this