Class map tag override

[raithedavion]

Description

Please provide a clear and concise description of your changes.
Explain what your PR does and why it's necessary.

I had a use case for using this in conjunction with a WYSIWYG editor, and I needed specific css classes that correspond to the editor to be mapped to specific styles in a template word document. So I made the required changes to the module and so far my local changes work very well.

Issue Reference

Link to the issue this PR addresses, if applicable.
Example: Fixes #123

Checklist Before Requesting a Review

• I have performed a self-review of my code.
• My code follows the project's coding style and guidelines.
• I have run tests and verified that all existing and new tests pass.
• I have added new tests to cover my changes.

[raithedavion]

Requested changes made. Let me know if you want me to pull down your current "HISTORY" or if you want to manually merge that file.

[dfop02]

Thanks @raithedavion , I'll review all again this weekend :)

[dfop02]

Hi @raithedavion !
I finally had time to review everything more carefully. I went through each part slowly and thoroughly. Thanks again for all your effort in helping make this project even better!

[dfop02]

Just a friendly reminder to review the updates on your PR. I left a few comments and also pushed the “html-comments” PR, so you’ll need to rebase and resolve the conflicts when you get a chance. Thanks!

[raithedavion]

Planning on getting it this weekend. Unfortunately had other priorities this week :D

[raithedavion]

Changes implemented.

[dfop02]

@raithedavion I could you remove all the lint changes you introduced, focusing just on you changes? Recently merged a new feature and it introduced some conflicts in a few files. Could you please merge the latest release/1.1.1 into your branch and resolve the conflicts?

Also, please be aware that PR #48 conflicts with some of your commits. I’m giving priority to reviewing and merging whichever PR addresses all changes and fixes first. You’re both doing a great job, and I’m looking forward to merging your contributions to help the project grow.

[dfop02]

@raithedavion Release 1.1.1 is officially out! 🎉
I created a new release branch release/1.1.2 for the next features, I know resolving the conflicts may have taken some time, so no worries. Some of the features you’re working on might already be covered by this release, please double-check, as it could address part of what you need.

Also, please remove the lint adjustments for now to avoid additional conflicts. I was following the flake8 rules, but it looks like the test workflow isn’t running correctly and needs to be fixed later. I’m also considering switching to another linter, so if you have any suggestions, I’m open to new ideas.

Let me know if you need any help or adjustments!

[raithedavion]

Ok. Think we got it v_v; finally.

[dfop02]

@raithedavion Great work! You forgot to change the target branch to release/1.1.2.
Please update it when you can and I’ll review everything again. 🙂

[raithedavion]

Done. Thought I had done that already lol

[raithedavion]

Done.

[dfop02]

Awesome! I'll review it all again still this week, thanks for all your efforts!

[dfop02]

hey @raithedavion I left 2 minor feedbacks, but looks pretty good, congrats!

[raithedavion]

Ok. All done. I moved the parse_line_styles & the previous releases _parse_text_decorations to utils (neither used "self" so it made sense to move it too). And I added the style clearing for the h1-9 tags.

[dfop02]

Awesome @raithedavion ! Merged!

I have one more planned task for this release that I'll probably work on this weekend, so I'm planning to release the 1.1.2 until next week, just for let you know.