Update dependency remark-flexible-markers to v1.2.1 #6436
Merged
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.
This PR contains the following updates:
1.0.4
->1.2.1
Release Notes
ipikuka/remark-flexible-markers (remark-flexible-markers)
v1.2.1
Compare Source
The changes made by @talatkuyuk
markerProperties
shouldn't have "className" key in the returned object, if there is, the plugin deletes the entry from returned object so as not to effect the<mark>
attributesv1.2.0
Compare Source
The changes made by @talatkuyuk
tsconfig.js
is updateddoubleEqualityCheck
is changed with theequalityOperator
actionForEmptyContent
option is added for empty content markers@types/mdast
is extended with theMark
typeTagNameFunction
andClassNameFunction
are added into the exported typeFlexibleMarkerOptions
in order the optionsmarkerTagName
andmarkerClassName
can take a callback functions respectivelycodecov
package-lock.json
file is added for fixing a github actionIt is more powerful now
As of version
^1.2.0
, theremark-flexible-markers
can handle also the syntax containing other markdown phrases like strong, emphasis, link etc. See https://github.com/ipikuka/remark-flexible-markers?tab=readme-ov-file#it-is-more-powerfullIt is more strict now
The double equity signs must be adjacent to the content. Here is an example for bad usage, and cause to not work.
It is more flexible now
The options
markerTagName
andmarkerClassName
can take a callback function in addition tostring
, now.For more information see https://github.com/ipikuka/remark-flexible-markers?tab=readme-ov-file#markertagname and https://github.com/ipikuka/remark-flexible-markers?tab=readme-ov-file#markerclassname
In addition to that, a new option
actionForEmptyContent?: "keep" | "remove" | "mark"
is added to handle mark syntax with empty content. See https://github.com/ipikuka/remark-flexible-markers?tab=readme-ov-file#actionforemptycontentPlease pay attention to a minor breaking change that the name of the option
doubleEqualityCheck
is changed with theequalityOperator
, the behavior is the same.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.