Hugo Peek
Hugo Peek
One thing I'm finding a bit tricky still, is renaming templates.. I want these names to be as clear as possible for clients, so sometimes I change their names to...
@JayCarney Thanks. Can imagine how that would be difficult to implement. Will survive without it though ;)
@DESIGNfromWITHIN I don't know why, but I'm using "elements" instead of "input_properties" for that.. So this still works for me: "elements": "Yes==yes||No==no",
Hmm, seemed to be a one-time glitch.. I think it was related to deleting an element that had been renamed before, but I didn't encounter this problem again.
Thanks for your explanation! I'm understanding how it works a bit better now, but it would still be great if this problem could be addressed somehow in a future release.....
Me too! I did run into an issue however, where using the same category name twice causes all the elements to be put in 1 category (#84). It looks like...
In addition: the categories are also being referenced by name in the .yaml file of every element..
I'm digging this one up and renaming it, because it keeps coming back as an issue in my projects.. The problem is that identical category names _in different parent folders_...
I'm also using this change for a while now, but just ran into an issue. I can't limit the extract to a specific context with the following config: ``` content:...