-
Notifications
You must be signed in to change notification settings - Fork 307
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Template Helpers #160
Comments
@rluders checkout the lambdas example: Docs here: https://mustache.github.io/mustache.5.html Your example would look like:
The python would be the same, afaik. Hope that helps! |
So, that's the example that I saw, but they only accept one parameter. They assume that everything between the template maker is a single parameter, when I need to pass multiple parameters. |
Not particularly elegant but I've always just done the parameter unpacking in the lambda itself e.g.
|
Yeah... Would be nice but I don't think it's been done in any of the mustache implementations that I've seen...nor in the spec. Probably that's due to putting "too much" data in the template. Could you make lambdas or prefilled data to serve this purpose? |
@kevincarrogan's example gets what you need. I think. If you wanted Not "idea" perhaps, but any change of this sort would have to happen upstream in the spec or via a pragma (first...then spec) to really get traction. The best thing about Mustache is that it's (relatively) consistently updated across languages. Keeping that intact is important for its future. |
So, that's how I'm doing today. I pass the values like this:
But I don't think that's looks elegant. Look, I think the follow syntax is so much elegant and great to read:
And maybe this discussion don't fit here, 'cause this is more about mustache specs then about pystache implementation or something like that. |
👍 for proposing this on the Mustache spec repo! It would (in some ways) bring Mustache close to Web Component style stuff as seen in Ember.js: Which look like this:
http://emberjs.com/guides/components/passing-properties-to-a-component/ Look familiar? 😄 Ping me on the issue you file, @rluders ! Would love to track it. |
Ember just use handlebars.js, which is itself a superset of mustache. There are ports of handlebars to python (pybars for example) that should work with your existing templates. The fact that mustache forces you to deal with these sorts of complicated transformations before hitting the template layer is a massive plus for me. I'd argue that you would be better to work your data into a shape that better suits your templates with a presenter or something. Theres plenty of room for both approaches. But I think this sort of sugar would run counter to the goals of mustache. |
Good call @carlmw. You're likely right. They feel "logicless" (as the logic happens elsewhere---sort of a partial + params), but...you may be right. Likely it's best to move the conversation to the spec repo and get the wider implementers involved. Though...this may not be the first time this was asked. :-P Who knows. :) |
@carlmw nice! I read about pybars, but the only problem is the fact that the 'handlebar' implementation for 'helpers' are not supported on mustache specs. So if I try to use my mustache templates with any other parser I'll be in a bad situation. I don't think as multiple parameters as a logic stuff, it's just a 'helper' to simplify some things that sometimes we have to do. I keep try to make all my logic on python server, but sometimes looks better if I could have some helpers on template site. I'll move this conversation to mustache specs, I think its better to us put all this thoughts there. |
@carlmw : I agree with your approach for staying to pure mustache. However, (adding you in @rluders ) pybars has an issue, it is LGPL. I would be ok if someone branched / forked pystache to started adding handlebars and handlebars helpers support. If that were to happen though, I'd like to see a mode the strictly enforces the mustache spec, since that's far more simpler and ubiquitous than hbs. |
Hi,
It's most a question and maybe a request.
It's possible to create a helper with parameters? Some like this sample:
The expected result is: Hello, Ricardo!
The text was updated successfully, but these errors were encountered: