Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clearer Configuration Options for Enum Types That Need Numerical Values #84

Open
Mrc0113 opened this issue May 13, 2021 · 1 comment
Open
Labels
documentation Improvements or additions to documentation enhancement New feature or request

Comments

@Mrc0113
Copy link
Contributor

Mrc0113 commented May 13, 2021

The Spring Cloud Stream Starter docs tell you to use the static variable values for specifying things like queueAccessType, but you can't actually use those (such as EndpointProperties.ACCESSTYPE_NONEXCLUSIVE) in the properties/yaml file. You need to specify the numerical value that it represents.

The fields like the ones below should be updated to state the default, but also the other options and what the valid numerical values are.

image

@Nephery Nephery added the documentation Improvements or additions to documentation label May 14, 2021
@Nephery
Copy link
Collaborator

Nephery commented Feb 3, 2022

Actually I wonder if Spring Boot can support multiple types. If it can, I wonder if we can add support for Enum values for each of these or resolve these "strings" into their real numerical values somehow.

I think this is something worth looking into when we come around to fix this.

@Nephery Nephery added the enhancement New feature or request label Feb 3, 2022
@Nephery Nephery changed the title Docs for Configuration Options Need Numerical Values Configuration Options Need Numerical Values Feb 3, 2022
@Nephery Nephery changed the title Configuration Options Need Numerical Values Clearer Configuration Options for Enum Types That Need Numerical Values Feb 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants