philcockfield
Routing
Hey,
I think it would be using to be able to share a URL to a component. For example if I'm creating an UI and want to share it with the designer.
BTW I'm loving this project.
Fitz
Thanks @fitz0019.
That's a good idea - I've often though about that and been balancing the needs of the component under test to "own" the URL, and the UIHarness to make components addressable by URL as you point out.
It would be a very good thing - especially for sharing/socializing/documenting components for the team to see and work with. Perhaps an opt-in (or opt-out) switch on the harness.
Some inspiration could be how Polymer's has their catalogue of elements for example https://elements.polymer-project.org/elements/paper-card. There are links to the document, demos and source of that element. The documentation is within a HTML comment as part of the element.
Polymer provide the code to create your own self documenting elements so all developers have a consistent experience. UI Harness could be that tool for React!
I understand UI Harness is about testing your component in isolation but I could see it being almost a living documentation of that component. This is probably out of scope of the issue I've raised where a URL would be nice :)
Totally see "living documentation of a component" as part of the value prop @fitz0019