Improve types of ScopeTuple

[mrjackdavis]

Description of the change

Fixes #11 by making a new inferable scope type.

I tried to edit ScopeTuple, but it's used in so many places and would've been a breaking change so I went for this approach

Type of change

• [x] Bug fix (non-breaking change that fixes an issue)
• [ ] New feature (non-breaking change that adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] Documentation or Development tools (readme, specs, tests, code formatting)

Links

N/A

Checklists

Development

• [x] Prettier was run (if applicable)
• [ ] The behaviour changes in the pull request are covered by specs
• [ ] All tests related to the changed code pass in development

Paperwork

• [ ] This pull request has a descriptive title and information useful to a reviewer
• [ ] This pull request has a Jira number
• [ ] This pull request has a Process.st launch checklist

Code review

• [ ] Changes have been reviewed by at least one other engineer
• [x] Security impacts of this change have been considered

[loganvolkers]

I've been trying to incorporate this code and add tests via https://github.com/ai/check-dts but it doesn't seem to work as you describe.

import { ScopeTuple, createScope, InferableScope } from "../";
const myScope = createScope<string|undefined>(undefined);

// Two type errors here
const myTuple2:InferableScope<string|undefined> = [myScope, "Foo"];

• myScope has the error: Type 'MoleculeScope<string | undefined>' is not assignable to type 'string | undefined'.ts(2322)
• "Foo" has the error: Type 'string' is not assignable to type 'never'.ts(2322)

What am I missing in your implementation?

[loganvolkers]

@mrjackdavis with the recent changes in Bunshi 2.1 it might not be relevant anymore.

Sorry that this PR sat around for so long. If you provide some context, I can add some Vitest type checks

[mrjackdavis]

All good 👍