Add support for endpoint field for WSDL version upgrade #19
Conversation
This file contains 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
simeon13
requested review from
alanso1996,
matthewdeol,
b6b and
andrewjleavitt
matthewdeol
approved these changes
Aug 14, 2023
alanso1996
approved these changes
Aug 17, 2023
b6b
approved these changes
Aug 22, 2023
ncperry
added a commit
that referenced
this pull request
Feb 1, 2024
In #19 we changed the default version but we never updated the specs accordingly.
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.
Currently, the WSDL versions after 2019.1 and after do not work because it is missing a necessary endpoint field. Without it, it errors out and our services do not work. This solution is referred to in this PR below.
NetSweet#473