-
Notifications
You must be signed in to change notification settings - Fork 40.9k
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
Add more anchors in the properties appendix #16267
Comments
I can see two ways we could fix this issue and both seems to lead to the creation of more tables. If we want to do this in a global fashion, perhaps our current description could have the notion of "sub-sections" so that we could do something like this:
That would create one sub-section under the current integration section with the same naming pattern (i.e. " If we don't want to go down that route, we could split things up a bit and just remove the high-level section and just listing the prefix one by one. In other words, remove the |
It is not just the Integration section; I see a similar problem in the Data section with hundreds of properties covering many technologies. |
It would be good to be able to link directly to a property from other documents. You need not have a heading for each anchor. Inline anchors can go anywhere. |
I've started working on something for this that will make each individual property linkable. |
Each property in the 2.4.0 snapshot docs now has an anchor and is a clickable link. For example, here's |
Sweet - thanks @wilkinsona |
Very nice. Thanks, @wilkinsona :) |
Although I agree, it's a very nice feature! |
It looks the same in Safari, I'm just less discerning than you. I think the main difference is that there's now a box drawn round each key. I think the CSS does that to any link where the text is monospaced (wrapped in `). |
spring-io/spring-doc-resources#48 needs to be addressed to fix this. We'll live with it in the meantime. |
Thanks for adding anchors to the appendix (#8237).
This is a big improvement, but I wonder if it could be a bit more granular; for example Integration Properties covers many technologies and properties.
It would be nice if we could jump directly to
rabbitmq
orkafka
instead of having to scroll past all the other properties.The text was updated successfully, but these errors were encountered: