Skip to content

added example of component mutating an already rendered property#1

Merged
GavinJoyce merged 1 commit intomasterfrom
gj/example-1
Dec 10, 2016
Merged

added example of component mutating an already rendered property#1
GavinJoyce merged 1 commit intomasterfrom
gj/example-1

Conversation

@GavinJoyce
Copy link
Owner

@GavinJoyce GavinJoyce commented Dec 10, 2016

screen shot 2016-12-10 at 12 37 01

@GavinJoyce
Copy link
Owner Author

Here's a nice tip from Kris Selden:

screen shot 2016-12-12 at 13 05 11


For this issue, here's how it helps:

  1. Put a breakpoint in assertNotRendered and note the key:

screen shot 2016-12-12 at 13 00 15

  1. Put a conditional breakpoint with the same key in didRender:

screen shot 2016-12-12 at 13 00 41

  1. Reload the app and you'll break at the original place where the value was first rendered:

screen shot 2016-12-12 at 13 01 14

  1. Navigate up the stack until to the currently executing opcode, you can determine the template from this information:

screen shot 2016-12-12 at 13 03 57

screen shot 2016-12-12 at 13 04 27

@bstro
Copy link

bstro commented Mar 12, 2018

What do you mean by "navigate...to the currently executing opcode" ?

@GavinJoyce
Copy link
Owner Author

GavinJoyce commented Mar 12, 2018

@bstro these are a little out of date, but should still help:

https://www.youtube.com/watch?v=vL8sCi1Bv6E&index=1&list=PLpAr6J-75N27wctNT70O0lubaGTPjwi1L

https://www.youtube.com/watch?v=l2nD1IxjHUI

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants