Ethan Resnick

Don't make `Tagged` type compatibility dependent on type fest version

5

Since removing `Opaque`/`UnwrapOpaque` is obviously gonna require a new major version, I wanted to put this PR up now, in case it makes sense to land both changes in the...

Remove Opaque/UnwrapOpaque

4

This PR may be premature, so I'm happy to let it sit for a bit. But, the basic idea is that: - Now that tag metadata has landed, `Tagged` types...

There are a series of tslint rules that could be good to use, but are too aggressive or too buggy at the moment. Those are: - promise-function-async - no-unsafe-any

Session handling

1

Finally add session handling, now that we know Twilio works with cookies well enough for us to use express-session.

allow non-renderable async states

2

I'm not sure what the harm is... [this would require updating `resolveBranches` to call backgroundTrigger as we branch over these non-renderable states, and it would require listing AsyncState explicitly in...

Imagine you have a state that reads the user their current bank balance, and that looking up this balance is quick enough that you don't need to render any intervening...

Remove EndState?

1

Pros: simpler type set. See no-end-state branch. Cons: makes it impossible to distinguish between an async state that is semantically an "end state" and an async state that isn't (i.e.,...

KFold(n_samples=n) not equivalent to LeaveOneOut() cv in CalibratedClassifierCV()

9

### Describe the bug Calling `CalibratedClassifierCV()` with `cv=KFold(n_samples=n)` (where n is the number of samples) can give different results than using `cv=LeaveOneOut()`, but the docs for `LeaveOneOut()` say these should...

Extend type predicate inference to work with certain type variables

2

### 🔍 Search Terms type predicate inference generic ### ✅ Viability Checklist - [X] This wouldn't be a breaking change in existing TypeScript/JavaScript code - [X] This wouldn't change the...

Query objects produce improper unhandled promise rejections in some cases

1

Jsforce Query objects have a dual identity as thenables and readable streams, which means there should be two ways to handle errors (in addition to the callback style): ```js query...