Matías Olivera
Matías Olivera
@jeroenrinzema Feel free to open a PR at this point! Just put in the description that is a work in progress
Let me try to answer all your questions separately: > If I were to create my own tower module, should I publish it on npm as a standalone package? Yes,...
Hello @shamuel22, I don't know, it shouldn't be. I'll investigate!
Hello @Zarel, just wanted to thank you for your contribution, and let you know that it didn't go by unnoticed. I'll be a bit busy for a couple more days,...
I'll gladly merge a PR that enables Korean! For reference: https://github.com/olistic/warriorjs/pulls?q=is%3Apr+is%3Aclosed+languages
Hello @Supermn54, thanks for your interest in the project! > Is this still open? As a newbie, I'd like to take this on if possible. Sure, I'll mark it as...
Assuming that you pass a `levels` array to the template, then you can simply do `levels.forEach(level => ...)` and render the [level partial](https://github.com/olistic/warriorjs/blob/e879fcd6fa3c47864e3fb01baa599dc891ac468e/packages/warriorjs-cli/templates/readme/level.ejs) inside the loop. Take a look at...
Ahh, gotcha. For the `data` object passed to the `ejs.render()`, we need to replace the level with an array of levels, as you said. And if I understood you correctly,...
So basically, when generating the README, we’ll create an array of levels which will have a single element when not in epic mode (the level with the number `profile.levelNumber`), or...
Hello @justdvnsh, that'd be awesome. How are you planning to tackle this?