Closed memorecks closed 3 years ago
Can be fixed when working on #16 and #31
Will need to consider adding testing for null--then output error indicating no matches found (the error message already exists on line 38.)
May also consider using regex for detecting sequence number or change syntax for indicating an optional sequence number. Maybe something like this:
!m[2] 0[0.5] 1[0.5] 2[0.5] -5[0.5]...
Where the number two contained within the brackets after the !m
is the sequencer number.
i prefer keeping it as !m2 and not !m[2] ... but if this needs to happen because of coding.. then all good! i think i've just trained myself to type !m1 and !m2 now lol
Just notating this here so I do not lose the idea. Solution to keep !m1, !m2, ... etc:
In tpts.paramamapper:
In parser.js:
Problem begins here: https://github.com/boomninjavanish/twitchPlaysTheSynth/blob/cda752cb9aee6f6ebeb8610e71a68debb3156dee/tpts.main/node_content/parser.js#L16
No matches occur when numbers are included