Hi
Thanks for all the feedback.
Yeah naming in IT is hard, and so is also which operator syntax to use.
{{?foo}} vs {{foo?}} vs {{optional:foo}} vs {{foo:-}}
I think the last one looks like a smiley ;)
And you can also think of using query parameters style:
{{foo?optional=true}}
On Tue,
Ah there is already the "?speedUp" notation to describe it as optional in
camel-main. Then I'm fine with {{?speedUp}} syntax to maintain consistency
within Camel.
https://camel.apache.org/components/latest/others/main.html#_optional_parameters_on_beans
On Mon, Mar 8, 2021 at 2:25 PM Tadayoshi
Hi Zoran,
Just in case, Properties component already provide the feature of
specifying a default value with {{speedUp:other}} syntax:
https://camel.apache.org/components/3.7.x/properties-component.html#_syntax
So what Claus proposes here is a feature that optionally can assign some
value but
Hi
I think if we want to go with ‘?’ as a marker for the optional parameter then
that question mark could be better put at the end of parameter name:
from("jms:cheese?concurrentConsumers={{speedUp?}}")
Like it’s the case in TS:
Hi Claus,
I like the bash shell parameter expansion[1], this allows for
specifying the default value if parameter doesn't expand. Something
like {{speedUp:-}} would be optional without a default value, whereas
{{speedUp:-other}} would provide `other` as a default value.
For the REST producer bits
