Skip to content
This repository was archived by the owner on Dec 25, 2024. It is now read-only.

Commit 122fc34

Browse files
committed
Switches list to breaks
1 parent ccee296 commit 122fc34

File tree

2 files changed

+6
-6
lines changed

2 files changed

+6
-6
lines changed

docs/generators/python.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ These options may be applied as additional-properties (cli) or configOptions (pl
2222
|generateSourceCodeOnly|Specifies that only a library source code is to be generated.| |false|
2323
|hideGenerationTimestamp|Hides the generation timestamp when files are generated.| |true|
2424
|library|library template (sub-template) to use: urllib3| |urllib3|
25-
|nonCompliantUseDiscriminatorIfCompositionFails|When true, If the payload fails to validate against composed schemas (allOf/anyOf/oneOf/not) and a discriminator is present, then ignore the compostion validation errors and attempt to use the discriminator to validate the payload. Note: setting this to true makes the generated client not comply with json schema because it ignores composition validation errors. Please consider making your schemas more restrictive rather than setting this to true. You can do that by: &lt;ul&gt;&lt;li&gt;defining the propertyName as an enum with only one value in the schemas that are in your discriminator map&lt;/li&gt;&lt;li&gt;setting additionalProperties: false in your schemas&lt;/li&gt;&lt;/ul&gt;|<dl><dt>**true**</dt><dd>If composition fails and a discriminator exists, the composition errors will be ignored and validation will be attempted with the discriminator</dd><dt>**false**</dt><dd>Composition validation must succeed. Discriminator validation must succeed.</dd></dl>|false|
25+
|nonCompliantUseDiscriminatorIfCompositionFails|When true, If the payload fails to validate against composed schemas (allOf/anyOf/oneOf/not) and a discriminator is present, then ignore the composition validation errors and attempt to use the discriminator to validate the payload.&lt;br/&gt;Note: setting this to true makes the generated client not comply with json schema because it ignores composition validation errors. Please consider making your schemas more restrictive rather than setting this to true. You can do that by: &lt;br/&gt;- defining the propertyName as an enum with only one value in the schemas that are in your discriminator map&lt;br/&gt;- setting additionalProperties: false in your schemas|<dl><dt>**true**</dt><dd>If composition fails and a discriminator exists, the composition errors will be ignored and validation will be attempted with the discriminator</dd><dt>**false**</dt><dd>Composition validation must succeed. Discriminator validation must succeed.</dd></dl>|false|
2626
|packageName|python package name (convention: snake_case).| |openapi_client|
2727
|packageUrl|python package URL.| |null|
2828
|packageVersion|python package version.| |1.0.0|

modules/openapi-json-schema-generator/src/main/java/org/openapitools/codegen/CodegenConstants.java

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -408,12 +408,12 @@ public static enum ENUM_PROPERTY_NAMING_TYPE {camelCase, PascalCase, snake_case,
408408

409409
public static final String NON_COMPLIANT_USE_DISCR_IF_COMPOSITION_FAILS_DESC =
410410
"When true, If the payload fails to validate against composed schemas (allOf/anyOf/oneOf/not) and a " +
411-
"discriminator is present, then ignore the compostion validation errors and attempt to use the " +
412-
"discriminator to validate the payload. " +
411+
"discriminator is present, then ignore the composition validation errors and attempt to use the " +
412+
"discriminator to validate the payload.<br/>" +
413413
"Note: setting this to true makes the generated client not comply with json schema because it ignores " +
414414
"composition validation errors. Please consider making your schemas more restrictive rather than " +
415-
"setting this to true. You can do that by: <ul>" +
416-
"<li>defining the propertyName as an enum with only one value in the schemas that are in your discriminator map</li>" +
417-
"<li>setting additionalProperties: false in your schemas</li></ul>";
415+
"setting this to true. You can do that by: <br/>" +
416+
"- defining the propertyName as an enum with only one value in the schemas that are in your discriminator map<br/>" +
417+
"- setting additionalProperties: false in your schemas";
418418

419419
}

0 commit comments

Comments
 (0)