Text modification config - #60
Open
rodneykinney wants to merge 5 commits into
Open
Conversation
rodneykinney
force-pushed
the
text-modification
branch
from
October 19, 2023 18:26
85c5401 to
a1a58ec
Compare
Member
Author
|
Not sure what's happening with automated tests. Maybe timing out?
|
This file contains hidden or 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
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 mixer configuration to trim trailing/leading whitespace from document text, and enforce a minimum document text length. Place these into a new
text_modificationconfig object, and move thespan_replacementsconfig into it.@soldni any objections to this backward-incompatible change to config structure?