Update soap to version 0.19.0 🚀#118
Open
greenkeeperio-bot wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hello lovely humans,
soap just published its new version 0.19.0.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of soap.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project ✨
You rock!
🌴
GitHub Release
Arrayif the namespace is already declared with another prefix. (#923)sequenceto field if it's defined within thecomplextType(#914)node-uuidpackage and use theuuid(successor) instead (#913)ejspackage version inpackage.json(#908)wsdlOptionsincreateClient()method (#901)eid) in emitted client events (#903)elementFormDefault=unqualified(#905)assertinstead ofshould()chain) intest/server-test.js(#906)test/request-response-samples/README.md(#900)The new version differs by 100 commits .
bd762ccRelease v0.19.03a1c6e9Fix missing namespace declaration on array if the namespace is already declared with another prefix. (#923)bc6992aFixes spelling error in WSSecurityCert-section. Changed the word 'succefully' to 'successfully' (#917)5dbcb1dadd fields sequence if it's required (need help) (#914)00ec5f1FIX deprecated node-uuid@1.4.7 (#913)54d20e8Only add references for the soap:Body and wsse:Security/Timestamp elements in WSSecurityCert (#911)daa4fb0Fix jshint error. (#909)8e37285Update the version of ejs dependency to ~2.5.5 (#908)a09fbd8Custom deserializer - allow to deserialize dates or any other type yourself. (#901)b4651ccadd the possibility to use our own exchangeId (#907)1a90a02Add exchange unique id in client events (#903)0d291a6Added option to suppress error stack in server response (#904)2ca1858Namespace prefix is required on first element when elementFormDefault=unqualified (#905)55e2614Fixed failing test since should have been using assert instead of should (#906)0544cc7Fix document error: wsdl_options.json, not .wsdl (#900)There are 100 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.