Cyril Silverman

We need to explicitly define the object lifecycle

2

Two major problems: - VexFlow has no clearly defined object lifecycle - VexFlow provides no support in assembling objects the right way This is something that that tests get really...

Default Style Audit - Bach Minuet in G

16

@0xfe has been [working on a simple full-score example in VexFlow](https://github.com/0xfe/vexflow/pull/437). Even though it's still in progress I thought this was a great opportunity to assess VexFlow's default style. Almost...

Improve Positioning API: Extract out current positioning code into stand-alone functions.

4

Currently, positioning in VexFlow is represented by various enums (eg. `Modifier.Position`) which map to specific code branches in each class. The user has absolutely no control over how each `Position`...

Enums defined outside the file are not parsed.

Cyclical `always` transitions result in "Maximum callstack exceeded" error

1

[This codesandbox includes a 2 state example.](https://codesandbox.io/s/eager-scott-edecu?file=/src/index.js:0-565) I've also experienced the same behavior with 3 states so assume it's related any cycle from `always` transitions. Additionally, the inspector doesn't render...

Here's the corresponding issue in `xstate-parser`: https://github.com/statelyai/xstate-parser/issues/8 Currently, any guards/actions used in these nested objects are being flagged as not used in the machine by the extension. Repro: https://codesandbox.io/s/zen-frog-d750i?file=/src/index.ts