Skip to content

Conversation

@jgrubb16
Copy link
Contributor

Type of change:

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update

Fix for #109 & #110

Builds on the work started in #124. Notably, my changes cause @coffeemakr's added tests to pass.
I noticed this regex pattern was repeated multiple times, so I chose to define it once for import. Not married to this approach. Open to your thoughts.

Copy link

@tharseken tharseken left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@andrenarchy
Copy link

@oozcitak Would you mind merging and releasing this fix? Thanks! 🙌

@universalhandle universalhandle merged commit 7af28ab into oozcitak:master Feb 24, 2023
@universalhandle universalhandle deleted the fix-109 branch February 24, 2023 15:13
@universalhandle
Copy link
Collaborator

Hello, folks. I'm a new co-maintainer for xmlbuilder2. I'll slowly be making my way through the backlog of pull requests and issues.

I've been talking with @oozcitak about transitioning some maintenance responsibilities to me, and as soon as I'm added as a maintainer on npm I'll ship this bug fix, which I've been using in production for several months.

@benasher44
Copy link

Exciting! This might also fix #117

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.

7 participants