Add an illustrative PR/issue tag

[paddymul]

There have been a bunch of small issues and pull requests here are very useful for future implementers, because they contain explanation of why things work as such. Ideally this would all be in documentation, until then, can we tag them with something like "illustrative PR".

There is a lot of context necessary for someone to use ipyreact, and it is going to be rare for someone to understand all of the following

• Traitlets quirks (only assignment - not updates to a dict, change must be present)
• React only assignment not updates to a dict
• Where JS errors show up in the jupyter notebook

#14
#11
#6

[paddymul]

Also I want to say, this is very impressive work by @maartenbreddels , I think this could really help increase jupyter widget creation, and build a bridge to the JS community.

If a normal frontend/JS developer comes to jupyter land to start trying to build stuff, they are confronted by a bunch of things that are new and novel to them (or reallly old like backbone.js). So they have to figure out widgets, traitlets, jupyter, possibly lumino, and lab extension packaging. Python itself is a mild hurdle compared to the rest.

This project limits that to

• widget/react data binding boundary (where all of these PRs and Issues are digging into)
• A very small amount of ipython magics that gives the frontend dev a much tighter OODA loop on JS changes

[maartenbreddels]

Thanks @paddymul ! (sorry for my late reply, just back from vacation!)

I like that! I invited you to 'triage' member of this repo. Let me know if that allows you to create labels.