NEW FEATURE: custom model field image prefix, custom filename and less duplication #192
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.
I needed some functionality that I think would be valuable to the base project if you are interested in any of it. The 3 feature changes are pretty simple.
This now gives developers and content creators 3 levels of customization without any overloading or extending this projects code.
The existing project level setting prefix MARKDOWNX_MEDIA_PATH + model/field level path prefix + imagename
I attempted to add the functionality with the least amount of changes or impact to existing or new installations.
I did not intend the comments to be kept but I thought it would be valuable during review to see why I think I needed each change.
An example of what a model field might look like:
An example of what a dropped image me.jpg final path might look like with the following settings:
/media/markdownx/2020/markdownpost/content/me.jpg
This is my first attempt at a pull request so if I did something wrong please let me know