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

Jump to bottom

fix code highlighting in concepts-models.md #124653

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

fix code highlighting in concepts-models.md #124653

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f6fab35
fix code highlighting in concepts-models.md
BartekSTRX Oct 15, 2024
9fe3989
Update concepts-models.md according to review suggestions
BartekSTRX Oct 17, 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 articles/digital-twins/concepts-models.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -166,7 +166,7 @@ Sometimes, you might want to define a relationship without a specific target, so

Here's an example of a relationship on a DTDL model that doesn't have a target. In this example, the relationship is for defining what sensors a Room might have, and the relationship can connect to any type.

:::code language="json" source="~/digital-twins-docs-samples-getting-started/models/advanced-home-example/IRoom.json" range="2-27" highlight="20-25":::
:::code language="json" source="~/digital-twins-docs-samples-getting-started/models/advanced-home-example/IRoom.json" range="2-30" highlight="22-27":::

### Properties of relationships

Expand All @@ -186,7 +186,7 @@ For a comprehensive list of the fields that may appear as part of a component, s

Here's a basic example of a component on a DTDL model. This example shows a Room model that makes use of a thermostat model as a component.

:::code language="json" source="~/digital-twins-docs-samples-getting-started/models/advanced-home-example/IRoom.json" highlight="15-19, 28-41":::
:::code language="json" source="~/digital-twins-docs-samples-getting-started/models/advanced-home-example/IRoom.json" highlight="18-22, 31-47":::

If other models in this solution should also contain a thermostat, they can reference the same thermostat model as a component in their own definitions, just like Room does.

Expand All @@ -212,7 +212,7 @@ The following example re-imagines the Home model from the earlier DTDL example a

In this case, Core contributes an ID and name to Home. Other models can also extend the Core model to get these properties as well. Here's a Room model extending the same parent interface:

:::code language="json" source="~/digital-twins-docs-samples-getting-started/models/advanced-home-example/IRoom.json" range="2-9" highlight="6":::
:::code language="json" source="~/digital-twins-docs-samples-getting-started/models/advanced-home-example/IRoom.json" range="2-10" highlight="9":::

Once inheritance is applied, the extending interface exposes all properties from the entire inheritance chain.

Expand Down