Feature: Use placeholder variables in filename filter

[Marty56]

It is not possible to filter filenames using placeholder variables.

[tfeldmann]

That's correct. It's an easy fix, expect it to land in the next update!

[Marty56]

The reason was that I wanted to calculate a placeholder that either contains the filename or some other string that is not matching. I was a workaround because I was not able to both return placeholders and True/False in the python filter. I have another issue open for this.

[mcurly]

@tfeldmann ,

Hi, and thank you very much for your tool.

Since I didn't see if this 'question' that I am posing right now has(n't) already been answered, I thought I ought to (well...) address it here.

I think it may be related to te OP issue. (But if @tfeldmann think it should be the topic for some other issue, be my guest and tell me so ok? And of course I'll create the topic for it there)...

The question is:

Which of the 'sections' (I call them that way, because I am by no means an 'expert', neither on python nor on your otherwise fantastic organize-tool) can be 'populated' by environment variables? Are these {env.VARS} only allowed in the locations 'keyword/section/list'?

I am assuming so, since I've been trying to put them on other 'keys' without any success.

For example:

(...) (snippet of configuration.yaml):
(..)
mimetype: {env.TYPES}
actions:
  - echo: "File of {mimetype} type found!" 

(With no useful yield beyond the Nothing to do. output :( )

My 'idea' or 'purpose' was to use the most generic configuration 'yaml' file that I could, for instance, in the 'organize edit' phase, and to be able with that to proceed to the 'sim'(ulation) or 'run'(ning) phases with more than 'Nothing to do.' ... outcome ;). I would love that one could export the needed variables, and be able to access them throughout the 'configuration.yaml' file. (I don't know if I am being clear about this).

Does this make sense to you @tfeldmann ?

Thank you.