Skip to content

Mark all pages for a deprecated package as deprecated #263

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

Open
alexanderkjeldaas opened this issue Sep 18, 2014 · 3 comments
Open

Mark all pages for a deprecated package as deprecated #263

alexanderkjeldaas opened this issue Sep 18, 2014 · 3 comments

Comments

@alexanderkjeldaas
Copy link

When a package is deprecated, it should not be necessary to go to the 'contents' section to see that it is deprecated.

The warning should be at the top of every page.

Here is an example: the following link is the first result for the query 'cprg hackage' on google. The package is deprecated.

http://hackage.haskell.org/package/crypto-random-api-0.2.0/docs/Crypto-Random-API.html

But that is nowhere to be seen, only on the main page:

http://hackage.haskell.org/package/crypto-random-api-0.2.0

See also haskell/haddock#328

@bananu7
Copy link

bananu7 commented Dec 16, 2014

This looks quite similar to #292.

@bitemyapp
Copy link
Contributor

@bananu7 deprecation is quite different from "not latest", but it's a similar idea. Adding the spot in the UI for one could enable the addition of a different, more urgent notice for the other.

@chrissound
Copy link

I think this would be really useful and informative. Though possibly a better approach is to deprecate all the modules within the package.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants