What makes it 'embedded' actually?
maybe it could be different types of template engines, basically differentiates embedded and logic less
@LeanKhan I just did a small post about embedded js template engines https://eta.js.org/blog/what-is-embedded-js-template-engine - hope it helps you understand :)
@shadowtime2000 also, can you show examples from other languages perhaps. Or the difference between embedded ones and those that are not embedded?
thank you @shadowtime2000, I'm using eta with express-flash. It is a mechanism that allows me to save messages throughout the code and present them to the user on the next pages...is there another mechanism that allows me to do this? It would appear that it works just fine if I don't call render
@dtrikannad you can even have them in a separate partial. Then you can also use them with a css framework that has alert components. You can also choose to use either cookie-sessions or regualr sessions. Hope this helps?
This is how I do it:
In my route... maybe after a login:
await req.flash('error', 'Something bad happened');
await req.flash('info', 'idk mehn, something happened sha');
await req.flash('success', 'Something good happened');
// bonus: I have this block in an app.use
// middleware so it captures all alerts for all routes
res.locals.alerts = {
info: await req.consumeFlash('info'),
error: await req.consumeFlash('error'),
success: await req.consumeFlash('success'),
};
Then in your template:
<% alerts.forEach(function(alert){ %>
<div>
<%= alert.message %>
</div>
<% }) %>You can come up with something better that fits for usecase tho
Of course you add the necessary checks and validations
@LeanKhan can you share which version of express-flash-message you're using? I've stepped in to the 2nd consumeFlash and req.session.flashMessage object is null. It gets nullified after the first consumeFlash call. On the first call, req.session.flashMessage contains all the messages, but once it returns, it seems to clear them all out and sets that object to null. any ideas? I'm using the latest 2.0.0
let sessionStore = new session.MemoryStore;
const sessionConfig = {
secret: '[secret goes here]',
name: 'appname',
resave: true,
saveUninitialized: true,
store: sessionStore,
cookie : {
sameSite: 'strict', // THIS is the config you are looing for.
maxAge: 60000
},
secure: false
};
app.use(session(sessionConfig));
@dtrikannad okay, you got express-flash to work? Nice one 👍
Just picked up Eta for something I'm working on so thought I'd tune in.
return res.render('pages/organization', {
user: req.user,
title: 'My Organizations',
organizations: orgDetails,
events: events,
errorMessages: await req.flash('error'),
infoMessages: await req.flash('info'),
successMessages: await req.flash('success'),
warningMessages: await req.flash('warning'),
dtFormat: require('dateformat')
});
where dtFormat takes in the require statement directly and that worked.
I was wondering if anyone who uses the eta-vscode extension for language support in vscode would be able to tel me which version of vscode they're using. It seems it's incompatible with my version (1.45.1).
@simonlayfield :wave: Hey, I created eta-vscode. I am running 1.54.3 and it seems to work fine for me
@/all Hey, I would just like to gather all your opinions on maybe transferring from Gitter to Discord. I find when using Gitter it is much harder to keep track of messages and get notified when they come. I think such a change would make it easier for people coming in to ask questions or give feature ideas and stuff because Gitter is not as organized.
