Add ng-empty-value attribute to ngOptions directive #13334

Activity

1. petebacondarwin

   added

   type: bug

   PRs plz!

   component: forms

   frequency: low

   needs: work

   needs: public api

   severity: inconvenient

   branch: 1.5.x

   on Nov 18, 2015
2. petebacondarwin

   added this to the 1.5.x - migration-facilitationThis milestone has been deleted milestone on Nov 18, 2015
3. Thesoro

   added 4 commits that reference this issue on Dec 8, 2015

   fix(ngOptions): add ngEmptyValue attribute to ngOptions

   ...

   9494295

   feat(ngOptions): add ngEmptyValue attribute to ngOptions

   ...

   a81ace4

   feat(ngOptions): add ngEmptyValue attribute to ngOptions

   ...

   490a3cb

   feat(ngOptions): add ngEmptyValue attribute to ngOptions

   ...

   b6fb9c3
4. Narretz commented on Apr 18, 2017

   

   Narretz

   on Apr 18, 2017

   Contributor

   More actions

   I think that this is not needed in core, as it can be simply and robustly implemented as a 3rd party module - see #1780 (comment) for more info. @gkalpak also agrees that this is not 100% necessary: #13471 (comment)

   👍React with 👍1Reacted by George Kalpakas
5. Narretz

   closed this as completedon Apr 18, 2017