Abubakar-Sattar opened a new pull request, #3282:
URL: https://github.com/apache/pekko/pull/3282

     ### Motivation
     Continuing from #3281. `sbt unidoc` reported 74 warnings after that merge. 
The next-largest clusters were bare
     `[[method]]` links to overloaded or private members — same bug class as 
#3281 — spread across the persistence
     module family (`persistence`, `persistence-query`, `persistence-tck`, 
`persistence-testkit`,
     `persistence-typed`).
   
     ### Modification
     Replace the bare `[[method]]` links with plain backtick text in 12 files 
(27 lines total):
     `deliver`/`initialize`/`DeleteMessagesTo`/`lastSequenceNr` in 
`persistence`,
     `readJournalFor`/`getReadJournalFor` in `persistence-query`, 
`DurableStateStore` in `persistence-tck`, five
     parenthesized links in `persistence-testkit`'s `TestOps.scala`, and one 
leftover in `persistence-typed`.
   
     ### Result
     23 targeted warnings resolved, verified by exact warning-identity diff. 
Total count moved from 74 to 61, not
     51, because fixing these revealed 10 previously-latent warnings elsewhere 
(all in the `stream` module, none
     touched by this change) — the same unidoc cross-module ordering effect 
noted in #3281. Those `stream` warnings
     are left for a separate PR since initial investigation showed fixing them 
cascades into revealing many more
     in `stream`/`stream-typed`, making it a much larger, separate effort.
   
     ### Tests
     - Not run - docs only.
     - `sbt "persistence/doc"` (and equivalent per-module checks) confirm the 
23 targeted warnings no longer
     appear.
     - `sbt -Dpekko.scaladoc.diagrams=false unidoc` (clean rebuild, run twice) 
confirms the count is stable at 61
     and the warning set is reproducible.
     - Native scalafmt not installed; ran `sbt scalafmtAll` per touched module 
instead - made no additional changes
     beyond the 27 targeted lines.
     - `git diff --check`: clean.
   
     ### References
     Refs #353


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to