Refactor: interface selections have proper location #107
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.
As described in #113, it's less than ideal that namespaces and interfaces are omitted from the
Locations
map, and therefore get handled as error side-effects:These missing locations bank on a not-obvious rule that they're not allowed to transition services, so can alway use their parent object's location. Ideally these known resources would simply route to known locations, and missing location errors would be treated as actual errors.
This adds interfaces to the
Locations
map so they become a properly routed resource.