Tom Spencer
Tom Spencer
@gitawego there are many issues with the current version on npm. I've just pushed a PR #95 to fix the issues. In the meantime you can use my branch which...
Hmm, I see, lots of similar changes are in #73. I'm happy to help out getting all of this lot merged together, the changes are fairly simple but very important,...
@rclayton-the-terrible I'm happy to maintain the codebase, at least for the time being, so it can be stabilised somewhat.
I'm happy to maintain if chosen.
What happened to the repo over the weekend? My fork appears to be 7 commits ahead of this repo. Did somebody force push changes? :disappointed:
@simison the tests are still failing on master. @Jokero what's the status of the repo?
On second thoughts, this is quite a simple plugin. I'm going to implement myself in my codebase, so thanks guys but I'm going to step away from the project now.
@macedigital I think mirroring the original express-body-parser options, with an extra `xmlOptions` property in the object would be best. ``` js { limit: '1MB', xmlOptions: { async: true, // etc...
Just to mention that I published [body-parser-xml](https://www.npmjs.com/package/body-parser-xml) a while ago, which fully supports the payload size limiting option, along with every other option that the main`body-parser` package supports.
I submitted a new PR, #136, with the conflicts fixed and the name changed (to 'pressable'). Hopefully it will be merged soon!