https://github.com/givanse/debug-and-report-a-bug-in-ember

debug and report a bug in Ember.js

Transcript

1. Ember JS Debug and report a bug
2. Gastón Silva @givanse http://givan.se Riot Games
3. Debug example Tools: • Ember inspector • Chrome developer tools Demo app: https://github.com/givanse/debuggin g-ember
4. Ember inspector Ember-inspector installation • Debugging promises ◦ Labels ◦ Stack traces
5. Chrome developer tools • Break point • Conditional break point • Continue until here Docs: Set a breakpoint on a particular line of code
6. Minimal test case You always need a reproducible test case. - demonstrate the problem to others - add a test once a fix is found Good test cases: Minimal code, inputs and outputs. Isolation, test only one thing. Strip out business logic. Help us help you. Suggested reading: StackOverflow MCVE
7. verify that your assumptions are true
8. Ember Twiddle https://ember-twiddle.com/ https://github.com/ember-cli/ember-twiddle Same file structure as Ember CLI Supports addons Save to gists and share
9. Twiddle examples Turns out: @each two levels deep is not supported However, we can still: Observe nested properties
10. Bad documentation is a bug [BUGFIX beta] Add warning for “deep @each” usage in dependent keys > WARNING: Dependent keys containing @each only work one level deep. You cannot use nested forms like todos.@each.owner.name or todos.@each.owner.@each.name. Please create an intermediary computed property.