feat: add set_file_path and set_base64_path functions #269
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rgonalo
reviewed
Feb 22, 2022
rgonalo
reviewed
Feb 22, 2022
|
Code Climate has analyzed commit 77a5709 and detected 0 issues on this pull request. View more on Code Climate. |
rgonalo
approved these changes
Feb 22, 2022
pabloge
deleted the
feat/add_set_file_path_and_set_base64_path_functions
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add set_file_path and set_base64_path functions to allow the use of the [BASE64:xxxx] and [FILE:xxxx] mapping patterns specifying a path that is relative to a base path previously set.
The current behaviour remains if no base path is set, i.e. the path specified in the pattern can be an absolute path or a path relative to the Python process execution path.