Programming CC-Diff: Automatically generate QC and GP checks (v0.3.5 @ #19)

https://zrp200.github.io/cc-diff/

I'm developing a web app that greatly eases writing C&C checks by doing all of the formatting for you. All you need is to give an "ideal" version of the analysis and it creates the check properly formatted. Colors are configurable, comments are addable, and it supports export to discord formatting as well.

I created this to make it possible to format checks while colorblind when I found that the existing tool was too imprecise.

The whole thing is coded with ReactJS.

Current Version: v0.3.5

Why use this?
  • Automatically formats checks
    • No need for the enraging menu searching or worrying about whether you formatted properly!
    • Eliminates the risk of entangling the original with your check
    • Guarantee consistent colors and formatting*
  • Always have a copy of the old version for reference while allowing free editing to create an "ideal" version.
  • Easier to share thanks to Markdown export option and ability to copy excerpts already formatted
  • Words are never split apart, making for an actually readable output.
  • Changes always are ordered in the form add remove comment
  • Capitalization changes are rendered as only changing that character if that's the only change of note.
    • Defensive defensive defensive
    • defensive Defensive Defensive
  • Hyphen changes are duplicated. By that, replacing "Arceus Fairy" with "Arceus-Fairy" and "switch-in" with "switch in" will yield Arceus Fairy Arceus-Fairy and switch-in switch in, respectively.
For QC
While most functionality is more useful for GP purposes, the app is still useful beyond auto-formatting checks:
  • If you store the new version of your check, and your check is implemented, you can compare it with the implemented check to generate a "changes" check.
  • Determine what changed when someone implements your check for easier evaluation.
  1. Generate your check.
  2. Keep the "New" section of the check (let's call it "Ideal")
  3. When your check is implemented, take the implementation ("Implement"), and put it into the "New" box.
    • You can also just use the original
  4. Put Ideal into the Old box to generate a check that points out all deviations from your check.
Features
Both have:
  • Saves inputs between sessions
  • Outputs both a visual diff as well as a copyable BBCode version for pasting.
  • Vaguely similar layout scheme
NEW:
  • Automatically generates output as you type
  • Configurable colors that are saved between sessions, and are easily reset to good defaults.
  • Hide the "old" box to focus on your changes.
  • Add underline and italics to checks to really make them pop!
  • Generate a color legend of the form add remove comment
  • Show paragraph markers in output, toggleable.
  • Allows comments delimited by {} in the New Box
    • Comments are automatically filtered out of the Old box for easier reuse of an "ideal" check with comments.
    • Comments can also be used to affect diff output, as they are considered dividers.
  • Toggle to automatically generate comments to distinguish easy-to-miss punctuation changes like periods, semicolons, and commas.
    This is highly configurable:
    • use add/remove color or the comment color for these. They will always be formatted like comments, however.
    • Toggle to omit removed punctuation entirely
    • Criteria for replacement can be either loose or strict
  • Copy excerpts from the preview directly, in addition to having the full export available.
  • Output in Markdown to post on Discord
  • Character Count that omits spaces, special for spotlights.
  • Quickly paste an analysis in, fill both boxes, and hide the old version in the same action.

Support the Developer
If you're interested in deeper development of this project, please support me:

Bugs, Comments or Concerns?
  • Post in this thread
  • DM me
A discord may be added if there is interest, but I'm on the Smogon, GP, and Natdex C&C servers, and you can contact me there as well.
My Discord is Zrp200
 
Last edited:
Please note that I have a strong tendency to rewrite the parser almost completely in every 0.X.0 change.

Anything that isn't explicitly documented as being part of the format is subject to change, either explicitly or implicitly via side effects of this, and app speed may similarly fluctuate.

If you notice the app responding dramatically slower after an update, please let me know.

While tests may keep previously fixed bugs from resurfacing, there's always the off chance that some edge cases may respond differently or that an established behavior was not assessed properly by the testing scheme. These are always fixed in patches as they are discovered.

v0.3.0: https://www.smogon.com/forums/posts/10181301/

v0.1.3
v0.1.0: https://www.smogon.com/forums/threa...nerate-qc-and-gp-checks.3743702/post-10131164
v0.0.2: fixed strikethrough output being white in some cases.
v0.0.1: comments are now ignored in the 'old' box.
  • Isolated "same" content can confusingly split an otherwise long change
  • Multiple hyphen changes in a long change can result in confusing results:
    * The Z-Move is best used on bulkier targets after setup, such as defensive Primal Groudon, Zygarde and support Arceus formes, rather than frailer targets. It is better to try such as Zacian-C or offensive Eternatus, since the latter two would be easier to remove with Shadow Force, especially since Zacian avoid using the boosted Z-C has a chance to be OHKOed by boosted Shadow Force after one layer of SpikesMove just for the sake of hitting in one turn against Pokemon that aren't defensive walls, and offensive Eternatus cannot OHKO Arceus-Ghost barring Tera Dragon Choice Specs Draco Meteor since said defensive walls will become significantly harder to break through.
    See the "to" splitting the remove, and see "Z-Move" being split incorrectly.
    A possible intended output here would be
    * The Z-Move is best used on bulkier targets after setup, such as defensive Primal Groudon, Zygarde and support Arceus formes, rather than frailer targets such as Zacian-C or offensive Eternatus, since the latter two would be easier to remove with Shadow Force, especially since Zacian-C has a chance to be OHKOed by boosted Shadow Force after one layer of Spikes, and offensive Eternatus cannot OHKO Arceus-Ghost barring Tera Dragon Choice Specs Draco Meteor. It is better to try to avoid using the boosted Z-Move just for the sake of hitting in one turn against Pokemon that aren't defensive walls, since said defensive walls will become significantly harder to break through.
  • Comments can sometimes break capitalization (caused directly by 0.3.0)
  • Immediate
    • Add Dark Mode support
    • Fix bugs
  • Medium
    • UI
      • Redo menus to be much more compact and modern, and moreover not have them be so bulky
      • Format properly on mobile devices
      • Link resources in the tool
    • Functionality
      • Configurable RC / AC messages, and add support for such for colons/semicolons
        • Partially completed in v0.3.0
      • Add bb code parsing support to better facilitate diffing and output formatting.
  • Long
    • Add a reverse option to implement checks automatically (generate "ideal" from a diff")
    • Add the ability to have add/remove/comment placeholders in old to allow overlaying checks upon others.
    • Make code open source
Also please do let me know if there's any oversights I made with formatting. It's a critical concern of this tool.
 
Last edited:
Few things that I would appreciate for this tool:
  • Enlargement of the font in each <textarea>; it feels like the size of the text boxes is much larger than what the design language of the rest of the page implies. I can comfortably read the text output but have to look more closely for all of the old, new, and BB Code text boxes.
  • I mentioned this in the Smogon Discord server already, but deleted punctuation shouldn't be completely omitted in the diff. If I delete a comma, I should see it in red, not just the (RC) after it would be.
  • Layout alterations
    • I would change the layout of the tool such that the "New" text box appears next to the "Output" text, since then I wouldn't have to scroll up and down to view the changes to the text.
  • Feature request: a way to export diffs to a Discord format, which I have found common when asking questions in the GP Discord. A common format I have used is bold (**text**) for additions and strikethrough (~~text~~) for deletions.
 
Hey, thanks so much!
Few things that I would appreciate for this tool:
  • Enlargement of the font in each <textarea>; it feels like the size of the text boxes is much larger than what the design language of the rest of the page implies. I can comfortably read the text output but have to look more closely for all of the old, new, and BB Code text boxes.
  • Layout alterations
    • I would change the layout of the tool such that the "New" text box appears next to the "Output" text, since then I wouldn't have to scroll up and down to view the changes to the text.
Yeah I'm aware the layout REALLY sucks. The tool....works. That's the stage it's in now.
Actually in the current stage of the project, I was actually having issues with the positioning of output to begin with, but I'll look into this (and possibly auto-scroll) when I figure out how to do this.
  • I mentioned this in the Smogon Discord server already, but deleted punctuation shouldn't be completely omitted in the diff. If I delete a comma, I should see it in red, not just the (RC) after it would be.
Hmm, really? I've been doing all my checks like the current format for a while now. I can make this happen, though. I'm also aware that the tags are being struckout in BB code, and I'll fix that as well.
  • Feature request: a way to export diffs to a Discord format, which I have found common when asking questions in the GP Discord. A common format I have used is bold (**text**) for additions and strikethrough (~~text~~) for deletions.
I can do this. Might end up restructuring the output area a bit and replace the remove the bbcode output box with a button to copy to clipboard for each supported format.
Technically I can support arbitrary formats with ease, but I haven't found a good use case for that.
 
I just updated the tool. New changes:
  • Markdown support
  • You can copy the text of the bbcode/markdown box by clicking on it.
  • Semicolons are now marked.
  • The tool is probably a bit slower and the layout is somehow worse :S
Edit: strikethrough was broken, so I just fixed it again.
 
Last edited:
Bug report: using the "Copy to Clipboard" button will delete any newline characters before copying.

Edit to avoid double posting: the diff placed a comma next to a semicolon instead of the correct location after a different addition.

Although uncommon, Magearna can also be used as a Trick Room setter on full-room teams as its defensive typing can allow it to set Trick Room multiple times since it doesn’t need to preserve bulk to sweep as its teammates typically serve that role.

Though uncommon, Magearna can also be used as a Trick Room setter on Trick Room teams, as its defensive typing can allow it to set Trick Room multiple times; on these teams, it doesn’t need to preserve bulk to sweep because its teammates typically serve that role.

AlthoughThough uncommon, Magearna can also be used as a Trick Room setter on full-room Trick Room teams, (AC) as its defensive typing can allow it to set Trick Room multiple times, (AC); on these teams since it doesn’t need to preserve bulk to sweep as because its teammates typically serve that role.

AlthoughThough uncommon, Magearna can also be used as a Trick Room setter on full-room Trick Room teams, (AC) as its defensive typing can allow it to set Trick Room multiple times; on these teams, (AC) since it doesn’t need to preserve bulk to sweep as because its teammates typically serve that role.

Essentially, the diff placed the comma before the "; on these teams" instead of after. I'm not sure if this is the fault of the diffing library you use or something else, but I figured that it should be noted here anyway.
 
Last edited:
  • Like
Reactions: BP
Bug report: using the "Copy to Clipboard" button will delete any newline characters before copying.

Edit to avoid double posting: the diff placed a comma next to a semicolon instead of the correct location after a different addition.

Although uncommon, Magearna can also be used as a Trick Room setter on full-room teams as its defensive typing can allow it to set Trick Room multiple times since it doesn’t need to preserve bulk to sweep as its teammates typically serve that role.

Though uncommon, Magearna can also be used as a Trick Room setter on Trick Room teams, as its defensive typing can allow it to set Trick Room multiple times; on these teams, it doesn’t need to preserve bulk to sweep because its teammates typically serve that role.

AlthoughThough uncommon, Magearna can also be used as a Trick Room setter on full-room Trick Room teams, (AC) as its defensive typing can allow it to set Trick Room multiple times, (AC); on these teams since it doesn’t need to preserve bulk to sweep as because its teammates typically serve that role.

AlthoughThough uncommon, Magearna can also be used as a Trick Room setter on full-room Trick Room teams, (AC) as its defensive typing can allow it to set Trick Room multiple times; on these teams, (AC) since it doesn’t need to preserve bulk to sweep as because its teammates typically serve that role.

Essentially, the diff placed the comma before the "; on these teams" instead of after. I'm not sure if this is the fault of the diffing library you use or something else, but I figured that it should be noted here anyway.
Fascinating. Will investigate. There's a post-processing step after the diff is generated to ensure that it adheres to expectations due to limitations of the library, and most of the issues tend to pop up there. Whitespace is annoying, and all symbol conversions are done at the last second.
 
Bug report: using the "Copy to Clipboard" button will delete any newline characters before copying.

Edit to avoid double posting: the diff placed a comma next to a semicolon instead of the correct location after a different addition.

Although uncommon, Magearna can also be used as a Trick Room setter on full-room teams as its defensive typing can allow it to set Trick Room multiple times since it doesn’t need to preserve bulk to sweep as its teammates typically serve that role.

Though uncommon, Magearna can also be used as a Trick Room setter on Trick Room teams, as its defensive typing can allow it to set Trick Room multiple times; on these teams, it doesn’t need to preserve bulk to sweep because its teammates typically serve that role.

AlthoughThough uncommon, Magearna can also be used as a Trick Room setter on full-room Trick Room teams, (AC) as its defensive typing can allow it to set Trick Room multiple times, (AC); on these teams since it doesn’t need to preserve bulk to sweep as because its teammates typically serve that role.

AlthoughThough uncommon, Magearna can also be used as a Trick Room setter on full-room Trick Room teams, (AC) as its defensive typing can allow it to set Trick Room multiple times; on these teams, (AC) since it doesn’t need to preserve bulk to sweep as because its teammates typically serve that role.

Essentially, the diff placed the comma before the "; on these teams" instead of after. I'm not sure if this is the fault of the diffing library you use or something else, but I figured that it should be noted here anyway.
fixed
 
I should release a new version of my tool relatively soon. Indev, I've made comment generation much more consistent (before it had a tendency to be slightly off or generate extra spaces), properly integrated the (AC) stuff so it consistently activates, and added toggleable paragraph markers.

It'll likely be slower again, but if there's continued interest I can run analytics on it.

I'm just working on the layout at the moment, and once I've got it to where I like it I'll release a new version.
I'm really not that experienced in layout making, so this might not be quite ideal, and I'll continue researching in the future.
OLD (1/4 total width)
Visual Output (1/2 total width)
NEW (1/4 total width)
Options
Hide Old box (makes above 0, 2/3, 1/3)​
Toggle Paragraph Symbols​
Other diff options​
Export
Export type (BBCode/Markdown)​
Copy Button
Preview of Export​
Colors
picker for ARC
Reset Color button​

I'm mainly responding to a noted desire to have the visual output adjacent to the new output, but also the current layout sucks and is absolute cringe....


Edit: this is what I have so far.
1716790935597.png

1716790998704.png
 
Last edited:
Just updated to v0.1.0

  • Eliminated lag almost entirely from diff algorithm
  • Algorithm is much more sensitive to whitespace
  • Fixed markdown output to actually.... work.
  • Algorithm no longer considers spaces right before a newline, which should remove some fringe added space markers
  • Added paragraph markers for the visual output. They don't appear when exporting, currently, however.
  • Comments are handled way more accurately and shouldn't cause any issues anymore ;)
    • Whitespace between the comment and the last text change no longer matters at all. (bugged lol)
    • The whitespace after still matters, however.
  • Symbols are handled a bit more consistently as well.
  • You can now hide the old box to use the diff window as reference instead; this gives more room to see things, as well.
  • Reduced font size of output.
  • UI below the text boxes is still WIP.
  • Misused comments are now just accepted until I figure out a good way to show it.
Known Issues that will be fixed soon:
  • space after ac, comments being omitted in output
  • capitalization sometimes consuming a trailing comma (fixed by adding a space between them)
  • replaced spaces being shown at all
v0.1.1 fixes the space issue for ac and also fixes weird capitalization logic. I also finally added tests for features to start to ensure that fixes don't accidentally get undone.
v0.1.2 fixes the the replaced spaces issue, and some cases where spaces are duplicated.

I'm still hunting for comment-related fixes. That's what I get for saying comments are "solved" lol
 
Last edited:
Aaaand I updated it again. Supposedly this is v0.1.3, but there's notable changes.

New options
  • Show paragraph markers in output (super experimental and probably slightly broken)
  • Use underline with adds and italics for removals in bbcode output. This really makes changes pop.
  • Disable symbol "emphasis" markers like (RC)
Other changes
  • The preview shown is now an exact preview of the output.
  • Added tooltips for most options.
  • You can now resize the boxes horizontally, and resizing the export textbox lets you move them up and down. Maybe at some point I'll merge the behavior.
  • If you click on the output preview and paste text, it will automatically fill both boxes with that text (if they are empty) and hide the old box, saving you several clicks.
    • If there's stuff in there, it'll ask you instead.
Fixes
  • I think I fixed comments again to increase their consistency. Or so the tests say....
  • A lot more text ordering issues, especially regarding comments.

Edit (v0.1.4): More fixes. I fixed an issue that was causing duplication of symbols (periods, commas, dashes, parentheses, etc) when chained. Also, I actually disabled ignoring whitespace this time, so spaces won't match tabs or newlines anymore..... (this is why paragraph breaks would sometimes be "lost" or "found" unexpectedly when there's a different number of breaks between versions. Ending whitespace is still ignored.
 
Last edited:
Been using this tool to do a lot of checks today, and it's really been helpful. A clear, readable output makes a tool like this easy to use, and it doesn't require reformatting the posts.

Would support for hyphen changes be possible? Changes like these aren't really visible without adding a comment alongside them.
1718223744334.png

1718223771245.png
 
Been using this tool to do a lot of checks today, and it's really been helpful. A clear, readable output makes a tool like this easy to use, and it doesn't require reformatting the posts.

Would support for hyphen changes be possible? Changes like these aren't really visible without adding a comment alongside them.
View attachment 640121
View attachment 640123
It's on the list of things to implement. It probably won't be in the next update, though.

For adds,
well-rounded
seems plenty readable to me, though it's fair to say that doesn't help with extra formatting toggled off, while the next update will change the logic for replacing a symbol like that with a space as
Ice-typing Ice typing

I haven't decided if it should be allowed to be alone; the current implementation will group it with related changes.
 
Last edited:
Your program is really helpful and intuitive—great stuff!

This is more of a quality of life change, but would it be possible to add a "Clear" button to wipe both the old and new text boxes simultaneously? It would be especially helpful when the original text is hidden (which is a great feature btw).

One other thing I noticed was that the underline/strikethrough formatting did not apply to punctuation. This is a relatively minor nitpick, but I think it would be especially useful if the formatting carried over if you implement the option to remove the (AC) and (RC) tags.

Screenshot 2024-06-12 at 11.42.52 PM.png

Screenshot 2024-06-12 at 11.43.12 PM.png

Screenshot 2024-06-12 at 11.47.47 PM.png
Overall, I really enjoy this, especially the underline and strikethrough formatting for additions and removals, respectively. Keep it up!
 
Thanks for your feedback, and I'm delighted that the app was handy!

One other thing I noticed was that the underline/strikethrough formatting did not apply to punctuation. This is a relatively minor nitpick, but I think it would be especially useful if the formatting carried over if you implement the option to remove the (AC) and (RC) tags.
So, this is actually a purposeful change, since the (AC) symbols are more like flavored comments and formatting looks terrible on these single characters.

My current thinking is to actually reduce the amount of these to only be placed in isolated cases, and lump them into an existing removal or addition's formatting if possible.

I've been going back and forth on having this be tied to the presence of italics/underline in the output, but the current plan detailed here doesn't take this into account.


This is more of a quality of life change, but would it be possible to add a "Clear" button to wipe both the old and new text boxes simultaneously? It would be especially helpful when the original text is hidden (which is a great feature btw).
I can add this to the next version. The button would be next to the hide old button.

Technically, the paste feature already does this, if you select a whole box and paste a new analysis in, but I can see the value of a dedicated clear button (and a swap button, to be honest).

I'm still tinkering with the box UI, and I would like to revamp it and add more quality of life features. In fact, those very features were set to be added at that point. Once I learn a bit more, I'll be adding buttons and features to the box area itself, but until then I'm trying to keep it relatively bare. I'll go more into detail about it when I release the next version.
 
v0.2.0
I've added a ton of features and fixed a lot of particularly annoying quirks of the app.
it's been up for several days now and I just got around to it now
1718572981277.png
New UI
150% size on my laptop
Output Preview
  • Preview Now Scrolls As You Type*
    When you type in either box, the preview scrolls to roughly where you were typing, so you don't have to worry as much about finding it later.
    This feature is not the most consistent at this time, and it has a tendency to have incorrect behavior when removing text in certain cases or toggling the color preview.
    If you continue typing, it will fix itself.
  • Copy From The Preview
    Copying from the preview converts only that portion to the selected format, allowing you to paste excerpts.
Options
  • Color Preview*
    Toggling this option will automatically add the typical formatting legend at the beginning
    *Name subject to change
  • Clear and Swap
    Added buttons to swap the content in the new and old boxes.
Misc UI/UX
I made some general attempts at UI improvements. I'm still learning but I believe it should be much better now.
  • General
    • Compressed some margins, improved some ordering overall.
  • Diff
    • Modified preview handling to avoid locking down the input boxes when there is a lot to render. It should dim slightly when it is doing this.
    • Fixed faulty pasting logic from the previous update. It should no longer clear your screen whenever you paste anything :S
  • Options
    • Grouped and labelled the options.
    • Improved organization of the sections. I may expand this type of formatting to the rest of the app.
  • Export
    • You can no longer copy by clicking on the export text box. Use the button instead.
    • Changed its resizing properties; the buttons above it no longer stretch when it is made larger.
    • The copy button now disables instead of hides when there is no output yet.
Ordering Rules
I've been working on driving out some particularly annoying output quirks:
Capitalization
  • Spd/SpD now yields "SpD" instead of "Sp D"
  • This also means that it now works for anycapitalization change, regardless of where it is in the word, as long as the only change in the word is the capitalization of its letters.
  • spd/SpD now yields "SpD"
Replacing punctuation like hyphens with a space
Punctuation being grouped together
Spacing incorrectly being generated around punctuation marks
  • Some punctuation marks like emdashes being given an extra space.
Leading/Trailing Spaces
  • Trailing and leading spaces at the very beginning and end of a box are now completely ignored.
 

Attachments

  • 1718570228011.png
    1718570228011.png
    1.2 KB · Views: 40
v0.3
(full descriptions + images WIP)
TLDR I rewrote almost all the output processing (again), added a bunch of options (and labels to options), and squashed a bunch of bugs.
Current version: 0.3.2
  • Fixed a catastrophically bad implementation of honoring punctuation locations.
  • Fixed copying from output duplicating all punctuation emphasis marks.
1720425385274.png
UI Additions
  • Character Count under each box, special for spotlights!
  • Version Indicator so these weird numbers I keep throwing out actually mean something!
  • Improved Options functionality! You can also hide them by clicking on the title or read a description of what they do by mousing over them.
Output
Punctuation Emphasis
  • Punctuation emphasis are now italicized in the same manner as comments.
  • The punctuation now are formatted regularly, instead of always lacking additional font styles other than color.
    1720421980178.png
  • Toggles
    • Omit Removed Punctuation renders removed punctuation without them actually being present:
      1720494960994.png
    • Use Comment Color makes them actually look like comments in output:
      1720422014416.png
    • Only Isolated only renders the markers when they are not associated with any other change.
      • On:
        Given what it hits its targets, Judgment is ran, run as well. (RP), (AC)
        This was the 0.2 default (I never announced it)
      • Off:
        Given what it hits its targets, (AC) Judgment is ran, (RC) run as well. (RP), (AC)
        This was the pre-0.2 default. The punctuation changes connected to "its targets" and "ran" are included here
Rules
  • Fixed Comments (yes it's true, and I haven't said this every update)
    • Comments had a habit of splitting changes arbitrarily and randomly deciding their locations based on magic.
    • That's gone now, because comments no longer consider spaces at all!
    • Also, all of the rules designated to make sure comments look right have been removed, since they're no longer needed, making them much, much less moody.
  • Replacing spaces with hyphens now duplicates the versions instead of merging them:
    1720421209283.png

    (This is disabled when either part of the word has been subject to a capitalization change)
  • Removed almost all space inference, which largely added spaces where they weren't supposed to, or worse, removed spaces that should have been there.
    The parser now defers to the actual text instead of making up where spaces should go itself. Such concept...
    • Various issues regarding spacing around capitalization changes and newlines have been fixed.
    • 1720421303666.png
      • Previously there was a space between "Therian" and "T"
      • There might be more changes on this front later, but at least now it doesn't imply a space between the dash and the addition.
  • Changes try to honor sentence dividers like commas and punctuation. Previously it was a matter of sheer luck. This is still a bit touch-and-go, so expect improvements here in the future!
Misc
  • Pasting directly from the forums no longer imposes extra spaces and weird paragraph marks.
  • Certain characters are now escaped when formatting Markdown, to ensure that they aren't accidentally used to format other text.
  • Fixed some other output issues with Markdown. There's still more, though. :psysad:

By the way, I'm rather color-blind, so any color scheme suggestions are welcome! I got a few requests to directly support dark/light modes, but I don't have the faintest idea how to coordinate the colors properly.


Edit #1: added some examples for some of the toggles and found a couple critical bugs while doing so
Edit #2: updated to 0.3.2, which fixes said critical bugs. removed the disclaimers.
 

Attachments

  • 1720421958685.png
    1720421958685.png
    7.4 KB · Views: 35
  • 1720422002933.png
    1720422002933.png
    1 KB · Views: 35
  • 1720494909979.png
    1720494909979.png
    11.9 KB · Views: 32
Last edited:
0.3.3 I have come to save the day!
  • hyphenated words are now never split during parsing. This should prevent all the bizarre malfunctions running around on that front, such as this incredibly cursed example:
    1721454882658.png
  • Words ending in "'s" are now never split during parsing:
    1721454206864.png
No more shall you have to fear hyphenated words or apostrophes!

0.3.4 fixes certain niche cases like this
1721514785971.png
 
Last edited:
Hello!

0.3.5 fixes:
  • some rare spacing issues if the first word includes a change, caused when having the legend on
  • some duplicated paragraph symbols when copying from the preview
  • markdown generating ¶____ for every added newline instead of __¶__
  • comments generating paragraph symbols.
I'm working on the next parser rewrite now, which when completed should cause the parser ---- or in other words, the algorithm will actually try to format things nicely to begin with, resulting in less bizzare one-off changes.
v0.3.0 already improved things on this end a lot, but I believe I can do better. Look forward to it!

  • Ability to highlight parts of the text.
  • option to auto-generate hide tags
  • Have color legend only specify the colors actually used (so it won't generate a tag for add if you didn't add anything)
(hopefully)
  • ability to hide any of the input boxes instead of just the old box
 
Last edited:
Any chance to add a mass find/replace option as a quality of life change over having to hop the results on another place for such purpose?
 
Back
Top