Vinay Sajip
Vinay Sajip
Have you tried `children.strip|length`?
Thanks, for the suggestion, Ben. Though that might work in this simple case, I'm not sure it's more generally applicable. According to the docs, `var` is > intended to be...
> and you'd prefer not to fork the package Well, you have to fork it to propose a PR :smile: and that's all I intended. > I have a feeling...
Is `props` documented somewhere, or an idea you're expressing? The documentation at https://mitchel.me/slippers/ doesn't appear to be searchable :disappointed: and I didn't come across `props`.
Sure, I agree that providing clarity for developers about how the system behaves is key. I made the change locally so I could progress the project where I'm using Slippers...
With the changes in my PR, I can illustrate the various possibilities. Assume the component `tester` is ```html {% var foo=foo|default:"Var foo" %} {% var bar=bar|default:"Var bar" %} In component,...
The reason for me suggesting that it be the default is that there is no other way of getting variable/parametric information into component content which is _not_ in subcomponents (whereas...
> Components will no longer be self-contained. Changing the component code could now have side-effects elsewhere in your code. That is always true, is it not? For example, a breaking...
Also, @mixxorz, what alternative method do you propose to address my use case in the initial post in this issue?
I've added a very simple configuration mechanism: if a file named `.pss` is found in the current directory, its contents are read in, treated as a list of command line...