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
Copy file name to clipboardExpand all lines: docs/book/v5/tutorials/find-user-by-identity.md
+10-11Lines changed: 10 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,8 @@
1
-
# Find user by identity - A practical example
1
+
# A practical example: Find user by identity
2
2
3
3
## Our goal
4
4
5
-
Create a new endpoint that fetches a user based on its identity.
5
+
Create a new endpoint that fetches a user record by its identity column.
6
6
7
7
We already have an endpoint that retrieves a user based on their UUID, so we can review it and create something similar.
8
8
@@ -37,12 +37,12 @@ This command will list all available endpoints, which looks like this:
37
37
### Note
38
38
39
39
> **The above output is just an example.**
40
-
>
41
-
> More info about listing available endpoints can be found [here](../commands/display-available-endpoints).
40
+
>
41
+
> More info about listing available endpoints can be found in `../commands/display-available-endpoints.md`.
42
42
43
43
The endpoint we're focusing on is the last one, `user.view`, so let's take a closer look at its functionality.
44
44
45
-
If we search for the route name `user.view` we will find its definition in the `src/User/src/RoutesDelegator.php` class, here live all user related endpoints.
45
+
If we search for the route name `user.view` we will find its definition in the `src/User/src/RoutesDelegator.php` class, where all user related endpoints are found.
0 commit comments