v1.0.2

Log less

v1.0.1

Docs

v1.0

Meta data

Merge branch 'next-component'

Macro

Documentation

New setter function

Attribute update

Fix attribute annotation

Annotate attributes

More attribute updates

Turn warnings back on

Validate attributes set on web component in JS

Validate attributes before setting

Getters and setters for attributes

New component macro

Fix id and attribute

Remove compoent threads with shared memory

I spent some time experimenting with threads and my conclusion
is that the restriction of not beeing able to lock on any
object in the main ui thread makes it more or less impossible.

Mainly because I don't know of a way to ensure that no wasm
code in the ui thread (deep down) calls Mutex::lock() and
ends up crashing the thread. Even things that seems to not
use any locking sometimes does.

Switching to web workers that posts messages instead.

Use thread local storage for components

Add component name to id

Fix component callbacks

New component impl

Fix indentation

Log less

Make attributes &str and use RwLock instead of Mutex

Get components from static storage

Remove counter test code

Fix rust init function

Id update

Update store

Fix error messages

Global store

Update component id

More callbacks

Update component id

Fix observer

Cleanup

Observed parameters

Detach web component

Fix incremented id

Refacor

Attach callback

Shorter function names

Fix and log init

Init functions

Rust side owner for the component

Add global component store

Make all components derive default

Fix init state functions

The rust self for component.

Init state function

Init functon from annotated struct