Add a configuration reference to the documentation that documents all the properties for this configuration. I'm not 100% sure how this is accomplished in micronaut-docs, but I believe the plugin may just be searching for any instances of @ConfigurationProperties in the src and then converting that to docs.
Using @ConfigurationProperties is likely preferable to just injecting single config values like I am doing, and I may want to switch to using that (especially if my above assumption is true). However, I don't think I'll be able to use it everywhere as I frequently using config values in other annotations.
┆Reporter: Joshua Carter
┆Issue Type: Story
┆Priority: High
┆Status: Backlog
┆Issue Number: MJ-40
┆Epic: Documentation
Add a configuration reference to the documentation that documents all the properties for this configuration. I'm not 100% sure how this is accomplished in micronaut-docs, but I believe the plugin may just be searching for any instances of @ConfigurationProperties in the src and then converting that to docs.
Using @ConfigurationProperties is likely preferable to just injecting single config values like I am doing, and I may want to switch to using that (especially if my above assumption is true). However, I don't think I'll be able to use it everywhere as I frequently using config values in other annotations.
┆Reporter: Joshua Carter ┆Issue Type: Story ┆Priority: High ┆Status: Backlog ┆Issue Number: MJ-40 ┆Epic: Documentation