Misleading documentation
See original GitHub issueTop Results From Across the Web
817.2341 False or Misleading Statements or Supporting ...
(3)(a) Any person who knowingly makes a material false statement or report to the department or office or any agent of the department...
Read more >Misleading documentation on provider configuration #30910
The documentation on configuring providers here seems to be incorrect. You can use expressions in the values of these configuration ...
Read more >Beware: Misleading Documentation Offers - Cruising World
Renewing documentation for most vessels is simple and straightforward, and costs $26 annually (renewal options for up to five years are also ...
Read more >Deceptive documentation in home healthcare nursing - PubMed
The discussion that follows examines this question by applying traditional principles of healthcare ethics to an individual case and offers one resolution to...
Read more >misleading documentation page title [35900851] - Issue Tracker
We've updated the documentation to be less misleading. The title for this page is now "Using third-party libraries." Thanks again for the report!...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Should probably make a point that, while
endTime
is documented, it doesn’t affect anything; i.e., there’s no actual code that does anything with it if received.endTime
is used nowadays https://github.com/freyacodes/Lavalink/blob/a3648335bc8838cb7d6cff6b5caacce35e3a70b1/LavalinkServer/src/main/java/lavalink/server/io/WebSocketHandlers.kt#L65I don’t see anything here that needs to be fixed