docs: fix javadoc tag resolution in markdown documentation#29
Conversation
Markdown does not evaluate Javadoc `{@value #CONSTANT_NAME}` syntax inside code blocks.
This updates `dlock-api/README.md` to reference the constants directly using
`KeyLock.MAX_LOCK_KEY_LENGTH` so the documentation is clear to developers.
Co-authored-by: pmalirz <19637300+pmalirz@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
1 participant
Replaced
{@value ...}Javadoc annotations with explicit literal constant references indlock-api/README.mdas standard markdown renderers do not expand them. Verified other READMEs do not have the same issue. Tests were executed to ensure no regressions.PR created automatically by Jules for task 4795074754925500423 started by @pmalirz