Skip to content

Commit

Permalink
Prettify
Browse files Browse the repository at this point in the history
  • Loading branch information
jason-fox committed Jun 4, 2024
1 parent f6be6d4 commit 70dc59d
Showing 1 changed file with 10 additions and 8 deletions.
18 changes: 10 additions & 8 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -211,6 +211,7 @@ This command will also import seed data from the previous
[Store Finder tutorial](https://github.com/FIWARE/tutorials.Entity-Relationships) on startup.

> [!NOTE]
>
> If you want to clean up and start over again you can do so with the following command:
>
> ```console
Expand Down Expand Up @@ -478,7 +479,7 @@ state.

This example reads the full context from an existing **Product** entity with a known `id`.

#### 7️⃣ Request:
#### 7️⃣ Request:

```console
curl -X GET \
Expand All @@ -505,7 +506,7 @@ Context data can be retrieved by making a GET request to the `/v2/entities/<enti

This example reads the value of a single attribute (`name`) from an existing **Product** entity with a known `id`.

#### 8️⃣ Request:
#### 8️⃣ Request:

```console
curl -X GET \
Expand Down Expand Up @@ -849,10 +850,11 @@ supplying the `type` parameter. Combine this with `options=count` and `attrs=__N
the given `type`.

> [!NOTE]
> The NGSIv2 specification specifies that `attrs=` has to be a "comma-separated list of attribute names whose
> data are to be included in the response". `id` and `type` are not allowed to be used as attribute names. If you
> specify a name that does not exist in attributes, such as `__NONE` to the `attrs=` parameter, No attribute will match
> and you will always retrieve only the `id` and `type` of the entity.
>
> The NGSI-v2 specification specifies that `attrs=` has to be a "comma-separated list of attribute names whose data are
> to be included in the response". `id` and `type` are not allowed to be used as attribute names. If you specify a name
> that does not exist in attributes, such as `__NONE` to the `attrs=` parameter, No attribute will match and you will
> always retrieve only the `id` and `type` of the entity.

## Update Operations

Expand Down Expand Up @@ -928,7 +930,7 @@ update.

This example uses the convenience batch processing endpoint to update existing products.

#### 1️⃣7️⃣ Request:
#### 1️⃣7️⃣ Request:

```console
curl -iX POST \
Expand Down Expand Up @@ -958,7 +960,7 @@ update.

This example uses the convenience batch processing endpoint to replace entity data of existing products.

#### 1️⃣8️⃣ Request:
#### 1️⃣8️⃣ Request:

```console
curl -iX POST \
Expand Down

0 comments on commit 70dc59d

Please sign in to comment.