For a long time I thought this was impossible to do without writing toString/fromString functions for your custom types, but I just realized that you can make it work by instead using the list index of the options as the "value", and then in the onChange decoder use that index to retrieve the item from the passed in options list.

Here's a demo: https://ellie-app.com/7253Q8THR2xa1

Hey, all!

As Zedux ramps up for its first pre-release (v0.1.0!), I just wanted to make a general request for feedback. Feel free to comment on this issue.

Some idea sparkers:

• How are you using Zedux?
• Do you see any flaws in the api? Anything that's unnecessarily difficult to use/remember?
• Is there any documentation that's unclear?
• Are there any examples you'd like to see?

Of

$ go test -cover -race ./...                                                              (328ms) 
ok  	github.com/SentimensRG/ctx	1.035s	coverage: 73.0% of statements
ok  	github.com/SentimensRG/ctx/mergectx	1.711s	coverage: 54.0% of statements
ok  	github.com/SentimensRG/ctx/refctx	1.032s	coverage: 75.0% of statements
?   	github.com/SentimensRG/ctx/sigctx	[no test files]

Currently, help functions accept any array of strings. It would be nice if help parameter can be narrowed down to specific union of string tuples.

For example: Let's say our application supports a main command and 3 subcommands which are foo, bar, and bar baz, then type of cmdPath parameter of help of main command should be [] | ['foo'] | ['bar'] | ['bar', 'baz']

Describe the bug
Docs have been rebuilt (again), and could use a second set of eyes on each page.

There don't seem to be any major errors, but there might be some weird quirks on some of the component page docs.

https://minerva-ui-docs.vercel.app/