Skip to content

Deprecation in Router Documentation #17905

Closed

Description

@ralemy

I'm submitting a ...


[ ] Regression (behavior that used to work and stopped working in a new release)
[ ] Bug report 
[ ] Feature request
[x] 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

Current behavior

In the router documentation page, under adding animations,

the code sample should be refactored, since AnimationEntryMetadata is deprecated and the rest have moved to angular/animations.

import { animate, AnimationEntryMetadata, state, style, transition, trigger } from '@angular/core';
export const slideInDownAnimation: AnimationEntryMetadata

Expected behavior

Should read:

  import { animate, state, style, transition, trigger } from '@angular/animations';
  export const slideInDownAnimation 

Minimal reproduction of the problem with instructions

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

Please tell us about your environment


Angular version: X.Y.Z

4.2.5
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. changed the title [-]Deprecation in Router [/-] [+]Deprecation in Router Documentation[/+] on Jul 3, 2017
  2. abdel-ships-it commented on Jul 3, 2017

    @abdel-ships-it

    I think it's safe to just remove AnimationEntryMetadata from the documentation.

  3. jasonaden commented on Jul 18, 2017

    @jasonaden
    Contributor

    @matsko Can you make a suggestion on this one?

  4. brandonroberts commented on Oct 13, 2017

    @brandonroberts
    Contributor

    This should be resolved once #19630 lands

  5. added a commit that references this issue on Nov 10, 2017
    d730321
  6. jasonaden commented on Dec 7, 2017

    @jasonaden
    Contributor

    Resolved with #20334

  7. mmatlock-shr commented on Mar 8, 2018

    @mmatlock-shr

    This is still an issue in current documentation for v5.2.8, #20334 is still an open pull request it looks like?

  8. angular-automatic-lock-bot commented on Sep 13, 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.

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

Metadata

Metadata

Labels

area: animationslegacy animations package only. Otherwise use area: core.area: router

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions