Not a workaround, but a solution. If you don't want to upgrade angular to a version that has this feature, you have to implement the feature yourself. So you can tell the management in the company that upgrading angular costs X, and developing just this feature costs Y. It's quite likely that Y in this particular case is significantly cheaper. But if you had two or three such features, X might turn out better in the long run. It's on them you decide, and on you to implement the decision.
Now, how would this work? Simple, create a directive that renders these options on your own, and then disables or enables specific options given the proper input data for the directive. Shouldn't be too hard, try it, and if you get stuck, let us know where you got stuck and somebody can take a look. -- You received this message because you are subscribed to the Google Groups "Angular and AngularJS discussion" group. To unsubscribe from this group and stop receiving emails from it, send an email to angular+unsubscr...@googlegroups.com. To post to this group, send email to angular@googlegroups.com. Visit this group at https://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
