-
Notifications
You must be signed in to change notification settings - Fork 223
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Correct rel used for a collection resource after upgrade to SD REST 2.0.1 #1
Comments
Where does this guide mention orders? I only see persons. |
Sorry, I mixed this up: yes, the server lists |
Okay got it. The annotation seems simple enough to show how customizable it is. Some of the guides were initially drafted "too" simple to be unreasonable, so we made them a little more realistic. Really becomes a matter of taste I guess. |
Whatever is fine for you? Maybe remove it for now to not expose the bug, and re-add it later on, when 2.0.1 has shipped? Simply waiting for 2.0.1 is perfectly fine as well, I think. |
If 2.0.1 is coming soon, let's just leave it there with this issue open. Then we can wrap it up then. |
Closed via 0230ae0, which brought the version of Spring Data REST up to 2.1.1.RELEASE. |
The guide discusses
orders
being used as rel in the_embedded
section after data has beenPUT
to the server. However, this is a bug in Spring Data REST as it should be consistent with the customized resource rel in@RepositoryRestResource
onPersonRepository
.I've filed and fixed DATAREST-261 so that we can tweak this once we shipped 2.0.1.
The text was updated successfully, but these errors were encountered: