Recursive tree

[daveyholler]

Summary

Easily render recursive tree structures such as file systems or outlines.

Checklist

• Checked in dark mode
• Checked in mobile
• Checked in IE11 and Firefox
• Props have proper autodocs
• Added documentation examples
• Added or updated jest tests
• Checked for breaking changes and labeled appropriately
• Checked for accessibility including keyboard-only and screenreader modes
• A changelog entry exists and is marked appropriately

[myasonik]

Roughly, summing up all of my suggestions, it think the final HTML would look something like this (rough pseudo-code):

<nav aria-label="Foo">
	<ul aria-label="Foo navigation">
		<li><ButtonOrLink>Bar<ButtonOrLink></li>
		<li>
			<ButtonOrLink aria-controls={randomId} aria-expanded={isThisNodeExpanded}>Baz<ButtonOrLink>
			<ul aria-label="Foo Baz navigation" id={randomId}> 
			// or, the label can be "Baz Foo navigation" if that seems more appropriate for the expected use case
				<li><ButtonOrLink>qux</ButtonOrLink></li>
			</ul>
		</li>
</nav>

Again, if this is not actually a way for users to navigate around the site, many of these suggestions are probably only half-way or completely incorrect.

[daveyholler]

The component fully supports keyboard navigation with left, right, up, down arrows, spacebar, and return.

[chandlerprall]

This just occurred to me... can we rename this component to EuiTreeView. This matches the design pattern instead of the recursion implementation detail.

[snide]

@daveyholler gonna pass you a PR for some quick design / interface changes. Nothing intense. FIgure it'll save you time so you can merge.

[snide]

PR4U @daveyholler daveyholler#8

[snide]

LGTM. Fun component. I'm gonna make a follow up issue to allow it to accept an href in certain situations. We can likely use this for the docs nav at some point.

[snide]

Confirmed with @chandlerprall this is mergeable.