Skip to content

fix: correct XML attribute name for after auto-spacing. #2975

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 14, 2025

Conversation

doublemix
Copy link
Contributor

Specifying true for ISpacingProperties.afterAutoSpacing is not working, but ISpacingProperties.beforeAutoSpacing is.

It seems to be caused by an incorrectly cased XML property name.

Local testing shows that this change allows after auto-spacing to be applied correctly.

Copy link

codecov bot commented Mar 14, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (b1f6765) to head (8a47a5e).
Report is 11 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff            @@
##            master     #2975   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          287       287           
  Lines         8387      8387           
  Branches      1410      1410           
=========================================
  Hits          8387      8387           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@dolanmiu dolanmiu merged commit ebae720 into dolanmiu:master Mar 14, 2025
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants