Skip to content
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.

Sign up for GitHub

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

Update README.adoc #130

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Update README.adoc #130

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
fbea57f
Update README.adoc
jnwelzel Sep 12, 2024
d9914a7
Update README.adoc
jnwelzel Sep 13, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions README.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -362,7 +362,7 @@ What needs to be done to make the REST architectural style clear on the notion t
____


The side effect of nnot including hypermedia in our representations is that clients must hard-code URIs to navigate the API. This leads to the same brittle nature that predated the rise of e-commerce on the web. It signifies that our JSON output needs a little help.
The side effect of not including hypermedia in our representations is that clients must hard-code URIs to navigate the API. This leads to the same brittle nature that predated the rise of e-commerce on the web. It signifies that our JSON output needs a little help.

[#_spring_hateoas]
== Spring HATEOAS
Expand Down Expand Up @@ -728,8 +728,8 @@ This class is similar to the previous version of `Employee`, with a few changes:
* A "virtual" getter for the old `name` property, `getName()`, is defined. It uses the `firstName` and `lastName` fields to produce a value.
* A "virtual" setter for the old `name` property, `setName()`, is also defined. It parses an incoming string and stores it into the proper fields.

Of course, not change to your API is as simple as splitting a string or merging two strings. But
itis surely not impossible to come up with a set of transforms for most scenarios, right?
Of course, no change to your API is as simple as splitting a string or merging two strings. But
it is surely not impossible to come up with a set of transforms for most scenarios, right?

[IMPORTANT]
====
Expand Down