Public API: allow null escalation chain when creating routes
#1557
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
vstpme
added
the
pr:no public docs
vstpme
removed
the
pr:no public docs
vstpme
changed the title
null escalation chain when creating routes via public APInull escalation chain when creating routes
iskhakov
approved these changes
Mar 16, 2023
# Conflicts: # CHANGELOG.md
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.
What this PR does
Allows passing
nullas a value forescalation_chainwhen creating routes via the public API.Which issue(s) this PR fixes
This is needed to unblock #1555 + creating a route without an escalation chain is possible in the web UI, so this PR makes the public API more consistent with the web UI.
Checklist
CHANGELOG.mdupdated