You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
/ and ~ are special characters in JSON Pointers, so when they need to be used literally (as part of a node name) they are encoded as ~1 and ~0, as per https://tools.ietf.org/html/rfc6901#section-3.
# Referencing a model named "foo/bar"$ref: '#/definitions/foo~1bar'definitions:
foo/bar:
...
However, in places where the model is referenced, the UI displays the model name incorrectly - still encoded using ~1 and ~0 instead of the actual name with /~.
Should those chars even be allowed as model names?
From a C# perspective (WebAPI) those chars are not possible, the models are coming from the name of the classes ...
This is a minor display issue related to #4152.
/
and~
are special characters in JSON Pointers, so when they need to be used literally (as part of a node name) they are encoded as~1
and~0
, as per https://tools.ietf.org/html/rfc6901#section-3.However, in places where the model is referenced, the UI displays the model name incorrectly - still encoded using
~1
and~0
instead of the actual name with/
~
.Demonstration API definition
Expected Behavior
Model names everywhere are displayed as
x/Foo
andx~Bar
.Current Behavior
In places where the models are
$ref
erenced, the model names are displayed asx~1Foo
andx~0Bar
instead ofx/Foo
andx~Bar
.Possible Solution
N/a
Context
Model names containing
/
and~
are displayed correctly in Editor v2:The text was updated successfully, but these errors were encountered: