If we don't have a value for a property we get below error. This error can be avoided by setting a colon : with or without a default value. Is there a way we can set default value for all the properties that way my application need not rely on the developer to specify :?

Could not resolve placeholder

If there is a better approach to solve this, please let me know.

Comment From: bclozel

Thanks for getting in touch, but it feels like this is a question that would be better suited to Stack Overflow. As mentioned in the guidelines for contributing, we prefer to use the issue tracker only for bugs and enhancements. Feel free to update this issue with a link to the re-posted question (so that other people can find it) or add some more details if you feel this is a genuine bug.

Comment From: gituserjava

@bclozel , responses on Stack Overflow are very slow. I have 3 questions out there for some spring questions and I don't have a single response and it's been more than 2 months. Instead of closing the ticket it would be great if you could tag the ticket as a question. Other Spring GitHub projects are doing the same. It is ideal to have questions, issues, enhancement under a project instead of scattering around internet.

Anyways I have posted the question on Stack Overflow as per your suggestion.

https://stackoverflow.com/questions/61970514/default-value-for-value-for-all-properties

Comment From: bclozel

I takes a bit of experience to ask a good question; I guess your questions will get more attention once they're more in line with the community's expectations.

I think your question could be improved with more context, explaining what you're trying to achieve, what you've done so far with minimal and concrete code snippets, the result you're seeing (a complete stacktrace or HTTP response for example) and what you expected instead.

The "for-stackoverflow" tag is our way to tag the issue as a question - we've got a global policy for Spring projects to handle community support on StackOverflow. I agree that the experience there is not always perfect, but the help of the Spring community there is very effective, the SEO is really good and unlike github, SO helps surfacing new/better answers for old questions.

Comment From: gituserjava

@bclozel , but when I asked the same 3 questions on Spring's GitHub page, they got answered within hours.

"for-stackoverflow" is good but if the ticket is closed, no one will attempt to answer.