Gary Burgess

Add optional property combinator

1

Partially resolves #29 - no record-based sugar for it still, but it's still useful in this form. /cc @gabejohnson @kritzcreek

`Set`, `NonEmptySet`, `NonEmptyString`, `NonEmptyArray` come to mind.

Add support for optional record properties

5

I have a rough thing that works for this using an `# optionalProp` combinator rather than the record syntactic sugar, but would like to come up with a way that...

I'm using `live-server` to serve static files and then have it proxying an API also, that API has a web socket endpoint, but it's unreachable at the moment as any...

Having the main component be a button is a bit misleading

4

While this repo isn't necessarily meant as a direct learning resource, it's still going to be the first thing some people encounter when trying to get hands-on with Halogen. Having...

Remove warning about shadowed value names?

13

This seems like much more of an opinionated lint-y thing than the other warnings we throw out. There are definite valid reasons for wanting to shadow names - for example,...

Reconsider merging exports and $foreign in psc-bundle

11

It's not a huge problem, but doing this makes all foreign functions public regardless of whether they're exported or not.

Consider `purs codegen` command

7

This was mentioned somewhere in the discussion about how to deal with `--dump-corefn`, etc. but the general ideal was the compiler could pick up the corefn and then perform JS...