Support non-extension patterns in ValueSchema file objects in Actions

[JosephVolosin]

Checked for duplicates

No - I haven't checked

Alternatives considered

Yes - and alternatives don't suffice

Related problems

No response

Describe the feature request

The pattern option for ValueSchema objects typed as file or fileList currently only allows pattern matching on the extension of a file. There should be a way to pattern match on the full filename.

For example, if I have a pattern \_TEST\_, then I would expect all filenames including the substring _TEST_ to match.

[duranb]

Do these _TEST_ files all have different extensions?

Currently, the purpose of the extension matching is to determine whether or not an action is applicable to certain files within a workspace. Is the desire to have an action only available if a _TEST_ file is present in the workspace or to have the action pre-populated with _TEST_ files?

[JosephVolosin]

In this case, yeah the _TEST_ files have the same extension - however that extension is just .txt, and for this specific action the only 'valid' files are those with _TEST_ in the filename, not just any .txt.

The desired function is essentially the same as the current functionality, but instead of treating the extension as the criteria for 'is the file applicable', we're treating the filename itself as the criteria.

[duranb]

And just to confirm, the filter for choosing the files is not sufficient right

?

[JosephVolosin]

Yes - what we ideally want is to pre-filter those results the same way by a pattern to stop users from accidentally choosing a file that doesn't work for the action.