e2068ad426
Ref: https://github.com/angular/angular.js/pull/4045 I have this sinking feeling that support this use case sort of encourages binding to function that blindly trust some html. For now, I'm fixing the issue while I think about the use cases some more. In the case of a function that performs any non-trivial work before wrapping the value (e.g. the showdown filter in issue #3980, or the binding to a simply wrapper function in issue #3932 if it did anything meaty), this fix makes it "work" - but performance is going to suck - you should bind to some other thing on scope that watches the actual source and adjusts itself when that changes (e.g. the showdown filter.) For the case of the wrapper in #3932, if one isn't performing sanitization or some such thing - then you the developer has insight into why that value is safe in that particular context - and it should be available simply by name and not as a result of a function taking any arbitrary input to make auditing of security a little saner. Closes #3932, #3980 |
||
|---|---|---|
| css | ||
| docs | ||
| example | ||
| i18n | ||
| images | ||
| lib | ||
| logs | ||
| src | ||
| test | ||
| .bowerrc | ||
| .gitignore | ||
| .travis.yml | ||
| angularFiles.js | ||
| bower.json | ||
| changelog.js | ||
| CHANGELOG.md | ||
| changelog.spec.js | ||
| changelog.tmp.md | ||
| check-size.sh | ||
| compare-master-to-stable.js | ||
| CONTRIBUTING.md | ||
| gdocs.js | ||
| gen_docs.sh | ||
| Gruntfile.js | ||
| init-repo.sh | ||
| jenkins_build.sh | ||
| karma-docs.conf.js | ||
| karma-e2e.conf.js | ||
| karma-jqlite.conf.js | ||
| karma-jquery.conf.js | ||
| karma-modules.conf.js | ||
| karma-shared.conf.js | ||
| LICENSE | ||
| package.json | ||
| README.md | ||
| release-commit.sh | ||
| start-iteration.sh | ||
| travis_build.sh | ||
| travis_print_logs.sh | ||
| validate-commit-msg.js | ||
| validate-commit-msg.spec.js | ||
| watchr-docs.rb | ||
AngularJS 
AngularJS lets you write client-side web applications as if you had a smarter browser. It lets you use good old HTML (or HAML, Jade and friends!) as your template language and lets you extend HTML’s syntax to express your application’s components clearly and succinctly. It automatically synchronizes data from your UI (view) with your JavaScript objects (model) through 2-way data binding. To help you structure your application better and make it easy to test, AngularJS teaches the browser how to do dependency injection and inversion of control. Oh yeah and it also helps with server-side communication, taming async callbacks with promises and deferreds; and make client-side navigation and deeplinking with hashbang urls or HTML5 pushState a piece of cake. The best of all: it makes development fun!
- Web site: http://angularjs.org
- Tutorial: http://docs.angularjs.org/tutorial
- API Docs: http://docs.angularjs.org/api
- Developer Guide: http://docs.angularjs.org/guide
- Contribution guidelines: http://docs.angularjs.org/misc/contribute
- Dashboard: http://dashboard.angularjs.org
Building AngularJS
Once you have your environment setup just run:
grunt package
Running Tests
To execute all unit tests, use:
grunt test:unit
To execute end-to-end (e2e) tests, use:
grunt package
grunt test:e2e
To learn more about the grunt tasks, run grunt --help and also read our
contribution guidelines.