question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Prevent deprecation warnings in documentation

See original GitHub issue

There’s few improvements to be done in Persistent Entity (scaladsl v1.3):

Example code in tests uses scalactic’s ConversionCheckedTripleEquals which is deprecated in favour of TypeCheckedTripleEquals.

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Comments:8 (8 by maintainers)

github_iconTop GitHub Comments

1reaction
TimMoorecommented, Jul 17, 2018

I just did a sneaky and updated the title to “Prevent deprecation warnings in documentation”, expanding the scope of the issue 😉. This actually just brings it in line with my comment above:

Let’s also make the documentation build fail on warnings once these are fixed.

The point is that we don’t want to demonstrate deprecated code in our documentation examples, now or in the future. Both Scala and Java compilers support options to fail on warnings, and we should set those in the documentation build.

@erip fixing warnings in docs/build.sbt itself (or anywhere else in the Lagom code base) is always appreciated, but not really the point of this issue.

In the case of LagomApplicationLoader, this is where deprecated code is used to maintain backwards compatibility, so I think it’s best to leave it alone until the deprecated API is removed in 2.0.

1reaction
TimMoorecommented, Apr 26, 2018

The code in question is in PostSpec.

You can see the deprecation warnings by running:

cd docs
sbt 'set scalacOptions += "-deprecation"' test:clean test:compile

See also #1282.

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to ignore deprecation warnings in Python - Stack Overflow
From documentation of the warnings module: #!/usr/bin/env python -W ignore:: ... Disable ALL warnings before running the python application.
Read more >
warnings — Warning control — Python 3.11.1 documentation
While within the context manager all warnings will simply be ignored. This allows you to use known-deprecated code without having to see the...
Read more >
Disable deprecation warnings in deprecated callables and types
What we want: first check whether bar is deprecated. If so, don't need to check foo. To do that, basically just need to...
Read more >
Dealing With Deprecations - GNOME Developer Documentation
One important thing to keep in mind is that 'deprecated' does not mean 'broken', or 'unusable'. There is no need to rush into...
Read more >
Enhanced Deprecation - Java - Oracle Help Center
Notifications and Warnings · @SuppressWarnings("deprecation") — Suppresses only the ordinary deprecation warnings. · @SuppressWarnings("removal") — Suppresses ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found