Missing exported components, hooks, utils, and types

Hi!

While playing with the lib, I noticed some absent exports to re-use. Why not to export as much as possible to be able extends on any level? Also, what about to use named exports (instead of defaults) to simplify index-exports? So, instead of

export { default as useLayoutNavigation } from "./useLayoutNavigation";

just export all:

export * from "./useLayoutNavigation";

I made some refactor for example on layout component, check it please, and if there is no objections from you, may be I can help with refactor.

https://github.com/aleksanderd/react-md/commit/c326fb2066a75d438f6466e55010520c2f5a29bb

Thank you!

[mlaursen]

I looked over this package again while writing the changelogs and realized it was never finished and was just hacked together to get the documentation site able to render. The latest commit (0dec760) should address some of the missing customization and I tried out the new <name>Props pattern which seems to work out pretty well. All the constants, types, utils, and additional components should now be correctly exported as well as some other few changes.

I’ll be updating the documentation a bit within the next few days, but the nice thing about these changes is that the Layout no longer requires the navItems and can be rendered as just a simple layout instead of a navigable layout. It also fixed some of the keyboard focus-loss and keyboard trap behavior that shouldn’t have been there.

[mlaursen]

Those changes sound good to me since it could also be applied to the <main> component and since there are too many props being passed down now. I think I’ll eventually apply this to other packages/components as well that have sub-components.