Skip to content

Conversation

@sonofmun
Copy link
Contributor

The @id key in the response from r_navigation is actually the url path to the current navigation request. Here I have changed the return for @id to the objectId and moved the url path that was in @id to a new dts:references key. This seems to make more sense to me but perhaps it doesn't conform to the standard.

The `@id` key in the response from r_navigation is actually the url path to the current navigation request. Here I have changed the return for `@id` to the objectId and moved the url path that was in `@id` to a new `dts:references` key. This seems to make more sense to me but perhaps it doesn't conform to the standard.
@sonofmun sonofmun requested a review from PonteIneptique May 15, 2024 13:29
@sonofmun
Copy link
Contributor Author

sonofmun commented May 15, 2024

@PonteIneptique If my changes comply with the expected behavior for the navigation endpoint, then I can also work to update the tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants