Added Forced Typing, a Testing Page, and Changed Booleans

Breaking Change

There are two breaking changes in this release. First, the way booleans are handled is slightly different. If you are using true / false values with web components, ensure that things are working as expected. Second, an optional second parameter for holding options is now available that allows you to force types. See the README for more information.

New Features

Force Typing

Want to bastardize event naming? Need to set those pesky booleans as attributes and properties? Really hate how you couldn't have one property be an attribute, property, and event handler? Say no more! With the new Options parameter, set to your heart's content! See the README for an updated example on usage

Examples and Testing Sandbox

Checkout the new tests folder to see examples of web components and their usage, including the new force options. Eventually this page will be used for Cypress tests

Special Thanks

Thanks to @nathfisher for his PR introducing forced typing