RFC: rename exportAs: 'form' to exportAs: 'ngForm' #5658

Activity

1. vicb

   added

   type: RFC / discussion / question

   on Dec 7, 2015
2. vicb

   assigned

   vsavkin

   on Dec 7, 2015
3. vicb

   added a commit that references this issue on Dec 8, 2015

   fix(form): Form directives are exportedAs 'ngForm' (was 'form')

   ...

   This issue will close once commit 24ad31b is merged into the 'master' branch.

   24ad31b
4. vicb

   closed this as completedin 8657ca4on Dec 8, 2015
5. user414 commented on Dec 11, 2015

   

   user414

   on Dec 11, 2015

   More actions

   I understand that we might not have time to update the angular.io site immediately, like in this case the hero form here

   https://angular.io/docs/ts/latest/guide/forms.html

   where it reference the old "form" but can we maybe tie them together with this in someway to keep track of them? On a side note beside looking at all the commits is there a way to find out non backward compatible commit such has this one? Could we perhaps add a label on the issue of commits so we could somehow easily extract a list of those for each alpha release? Thanks.
6. pkozlowski-opensource commented on Dec 11, 2015

   

   pkozlowski-opensource

   on Dec 11, 2015

   Member

   More actions

   On a side note beside looking at all the commits is there a way to find out non backward compatible commit such has this one?

   See https://github.com/angular/angular/blob/master/CHANGELOG.md and pay attention to the "Breaking changes" section
7. user414 commented on Dec 11, 2015

   

   user414

   on Dec 11, 2015

   More actions

   Great thanks, exactly what I was looking for, was in a too obvious place:-)
8. user414 commented on Dec 11, 2015

   

   user414

   on Dec 11, 2015

   More actions

   So is the subsequent task to update the angular.io somewhere else as well and I can't see it?
9. user414 commented on Dec 11, 2015

   

   user414

   on Dec 11, 2015

   More actions

   If it is someone can just mark the one I opened as duplicate, thanks.
10. angular-automatic-lock-bot commented on Sep 7, 2019

    

    angular-automatic-lock-botBot

    on Sep 7, 2019

    More actions

    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. angular-automatic-lock-bot

    unassigned

    vsavkin

    on Sep 7, 2019
12. angular-automatic-lock-bot

    locked and limited conversation to collaborators on Sep 7, 2019