@@ -111,6 +111,7 @@ SYNOPSIS
111
111
sonata-blending-tool-cli blend
112
112
[ {-b | --blending-schema} < specifications to be blend (integrate) in> ... ]
113
113
[ {-d | --spec-root-dir} < root directory for specifications to be blended> ]
114
+ [ {-discover | --auto-discover} ]
114
115
[ {-e | -e ncoding} < files encoding> ]
115
116
[ {-f | --force-override} ] [ {-i | --input-spec} < spec file> ]
116
117
[ {-m | --model-name} < model to be augmented> ]
@@ -127,14 +128,16 @@ OPTIONS
127
128
This option is part of the group ' allOrSelective' from which only
128
129
one option may be specified
129
130
130
-
131
131
-d < root directory for specifications to be blended> , --spec-root-dir
132
132
< root directory for specifications to be blended>
133
133
root directory for specifications.
134
134
135
135
This option may occur a maximum of 1 times
136
136
137
-
137
+ -discover, --auto-discover
138
+ Try to use a parent type name from x-mef-target extension in
139
+ schema. If not defined the fallback is to take ' model-name'
140
+
138
141
-e < files encoding> , -encoding < files encoding>
139
142
encoding used to read API and product definitions. By default
140
143
system encoding is used
@@ -210,6 +213,14 @@ Assumption is that this command is run from root of the Legato SDK directory and
210
213
-b carrierEthernetSubscriberUni.yaml
211
214
` ` `
212
215
216
+ # ## Additional features
217
+
218
+
219
+ # ### Auto-discover mode
220
+ If a schema to blend defines ` x-mef-target` extension it can be used as a target class name for given type.
221
+ To enable this feature please use ` -discover` flag. In auto-discover mode if ` x-mef-target` is not defined for the schema
222
+ the ` model-name` will be used as a fallback.
223
+
213
224
# # Tool `merge` command synopsis
214
225
215
226
Merge command generates an OAS 3 definition that is a minimal OAS file including ` components/schemas` only
@@ -220,6 +231,7 @@ SYNOPSIS
220
231
sonata-blending-tool-cli merge
221
232
[ {-b | --blending-schema} < specifications to be blend (integrate) in> ... ]
222
233
[ {-d | --spec-root-dir} < root directory for specifications> ]
234
+ [ {-discover | --auto-discover} ]
223
235
[ {-f | --force-override} ]
224
236
[ {-m | --model-name} < model to be augmented> ]
225
237
{-o | --output} < Output file name> [ --sorted ]
@@ -239,7 +251,10 @@ OPTIONS
239
251
240
252
This option may occur a maximum of 1 times
241
253
242
-
254
+ -discover, --auto-discover
255
+ Try to use a parent type name from x-mef-target extension in
256
+ schema. If not defined the fallback is to take ' model-name'
257
+
243
258
-f, --force-override
244
259
245
260
0 commit comments