Skip to content

Commit 6646e69

Browse files
committed
incorporate feedback
1 parent 546dbb8 commit 6646e69

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

articles/azure-resource-manager/bicep/user-defined-data-types.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: User-defined types in Bicep
33
description: Describes how to define and use user-defined data types in Bicep.
44
ms.topic: conceptual
55
ms.custom: devx-track-bicep
6-
ms.date: 09/22/2023
6+
ms.date: 09/26/2023
77
---
88

99
# User-defined data types in Bicep
@@ -246,6 +246,8 @@ param serviceConfig ServiceConfig = { type: 'bar', value: true }
246246
output config object = serviceConfig
247247
```
248248

249+
The parameter value is validated based on the discriminated property value. In the preceeding example, if the *serviceConfig* parameter value is of type *foo*, it undersoes validation using the *FooConfig*type. Likewise, if the parameter value is of type *bar*, validation is performed usin the *BarConfig* type, and this pattern continues for other types as well.
250+
249251
## Import types between Bicep files (Preview)
250252

251253
[Bicep version 0.21.1 or newer](./install.md) is required to use this compile-time import feature. The experimental flag `compileTimeImports` must be enabled from the [Bicep config file](./bicep-config.md#enable-experimental-features).

0 commit comments

Comments
 (0)