Skip to content

API index status filter does not apply when viewing only packages #25708

Closed

Description

@jenniferfell

I'm submitting a...


[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
[X] Other... Please describe: AIO behavior of API index page filtering

Current behavior

https://angular.io/api?status=security-risk&type=package
If you filter the API reference index by type=package, the status filter does nothing. No matter what status filter option is chosen, all packages are displayed.

Expected behavior

Some options:

  1. Disable status filter, so it's clear that it doesn't apply when type=package
  2. If entire packages do have a status, find a way to encode that so we can enable status filter and have it behave the same way it does for individual types
  3. If a package's status can be derived from its exports, then use the types to determine package status? I'm not sure if this one makes sense, but I could imagine "type=package & status=security risk" returning every package that has at least one export for which status=security risk.

Minimal reproduction of the problem with instructions

  1. Go to angular.io/docs
  2. Choose API from left nav
  3. Choose type=package
  4. Choose status=security risk
    All packages are listed.
  5. Choose status=deprecated
    All packages are listed.

https://angular.io/api?status=security-risk&type=package

What is the motivation / use case for changing the behavior?

To cause package list to match selected filter settings.

Environment


Angular version: X.Y.Z


Browser:
- [ ] Chrome (desktop) version XX
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
 
For Tooling issues:
- Node version: XX  
- Platform:  

Others:

Activity

  1. added this to the needsTriage milestone on Aug 28, 2018
  2. jenniferfell commented on Aug 28, 2018

    @jenniferfell
    ContributorAuthor
  3. petebacondarwin commented on Aug 29, 2018

    @petebacondarwin
    Contributor

    As far as I am aware packages do not have their own "status" states, and I don't know how one would compute the state from exports which can be mixed within a package (e.g. some exports could be experimental, while others are deprecated).

    So until we decide to apply these states to packages as a whole, I will implement the first option given by @jenniferfell, which is to disable this drop-down when the type is being filtered as "package".

  4. added a commit that references this issue on Aug 29, 2018
    fd347d3
  5. IgorMinar commented on Aug 30, 2018

    @IgorMinar
    Contributor
  6. modified the milestones: needsTriage, Backlog on Aug 30, 2018
  7. modified the milestones: Backlog, v7.0 on Aug 30, 2018
  8. petebacondarwin commented on Aug 31, 2018

    @petebacondarwin
    Contributor

    @IgorMinar is that marked in some way in the source code?

  9. added a commit that references this issue on Sep 5, 2018
    6f7df8a
  10. angular-automatic-lock-bot commented on Sep 14, 2019

    @angular-automatic-lock-bot

    This issue has been automatically locked due to inactivity.
    Please file a new issue if you are encountering a similar or related problem.

    Read more about our automatic conversation locking policy.

    This action has been performed automatically by a bot.

  11. locked and limited conversation to collaborators on Sep 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions