Conversation
… output in the correct type (boolean/number)
Contributor
|
🌟 Thank you for your contribution to the Apache Camel project! 🌟 🤖 CI automation will test this PR automatically. 🐫 Apache Camel Committers, please review the following items:
|
Contributor
Author
|
@lordrip here is a PR where the defaultValue is according to the type |
oscerd
approved these changes
Oct 29, 2025
lordrip
approved these changes
Oct 29, 2025
Croway
approved these changes
Oct 29, 2025
lordrip
added a commit
to lordrip/camel-catalog
that referenced
this pull request
Oct 30, 2025
In Camel 4.15, the `default` values are written in `string`, regardless of its type. For instance, this is how the `scriptPropertyPlaceholders` property is defined, notice the `default: "true"` portion.
```
"scriptPropertyPlaceholders" : {
"type" : "boolean",
"title" : "Script Property Placeholders",
"description" : "Whether the script should support using Camel property placeholder syntax {{ }}.",
"default" : "true"
},
```
This commit fixes this issue at the Entity and Pattern level by
adjusting the default value to its right type.
A fix for this was provided in Camel upstream here: apache/camel#19753
This was referenced Oct 30, 2025
lordrip
added a commit
to lordrip/camel-catalog
that referenced
this pull request
Oct 30, 2025
In Camel 4.15, the `default` values are written in `string`, regardless of its type. For instance, this is how the `scriptPropertyPlaceholders` property is defined, notice the `default: "true"` portion.
```
"scriptPropertyPlaceholders" : {
"type" : "boolean",
"title" : "Script Property Placeholders",
"description" : "Whether the script should support using Camel property placeholder syntax {{ }}.",
"default" : "true"
},
```
This commit fixes this issue at the Entity and Pattern level by
adjusting the default value to its right type.
A fix for this was provided in Camel upstream here: apache/camel#19753
lordrip
added a commit
to KaotoIO/camel-catalog
that referenced
this pull request
Oct 30, 2025
In Camel 4.15, the `default` values are written in `string`, regardless of its type. For instance, this is how the `scriptPropertyPlaceholders` property is defined, notice the `default: "true"` portion.
```
"scriptPropertyPlaceholders" : {
"type" : "boolean",
"title" : "Script Property Placeholders",
"description" : "Whether the script should support using Camel property placeholder syntax {{ }}.",
"default" : "true"
},
```
This commit fixes this issue at the Entity and Pattern level by
adjusting the default value to its right type.
A fix for this was provided in Camel upstream here: apache/camel#19753
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
… output in the correct type (boolean/number)
Description
Target
mainbranch)Tracking
Apache Camel coding standards and style
mvn clean install -DskipTestslocally from root folder and I have committed all auto-generated changes.