Skip to content

Conversation

mfathi91
Copy link

No description provided.

Copy link
Owner

@dsaltares dsaltares left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the contribution but the proposed change does not fix the documentation.

I've left a comment indicating that the real behaviour is. I would merge a change to clarify the current behaviour though.

### `regex`

Boolean indicating if `file` is to be interpreted as regular expression. Defaults to `false`.
Boolean indicating if `true` is to be interpreted as regular expression. Defaults to `false`.
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The current README is correct though. This option controls wether the file parameter should be interpreted as a regex or a literal file name.

Perhaps the documentation could be a bit clearer.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello @dsaltares,
Thanks for the explanation. So if the user wants to use the regular expression functionality for a file (e.g. my-file-.*.zip instead of my-file-4.0.1.zip) should the regex parameter be true or false?

I was under the assumption that it should be true for regular expression behavior.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants