Add typescript

[manthanabc]

Add support for typescript

WHY?

the variables types are very flexible and inconsistent across the project especially in the engine.js file so adding typescript would really help out removing the type confusion when passing around state objects

[CodeStrate]

I can help move from js to ts. Can I be assigned? Let's discuss more about the requirements and the issues you're facing with flexible types that need to be resolved, if it's anything but confusion.

[manthanabc]

Sure, I'll assign it to you. If you need any help feel free to ask

[CodeStrate]

@manthanabc I was looking at the code base, so I got some doubts:

• Do you want to transition the entire JS logic towards TS (adding type safety)?
• I was dabbling in your Pages deployment, and I noticed that the Parser doesn't detect + as an operation, rather it stores them in a state as if they are symbols. ^ and | work fine. Also * but it's a lot of parentheses.

Example

I only got this expression to yield a good result

Also, this,

simpler expressions like (ab+ba)* yield a straight line. Also (a|b)*

[CodeStrate]

Example of what doesn't work as expected

(ab+ba)* should be

[manthanabc]

Yeah so the input app expects is not exactly regex
consider your example (ab + ba)* should produce

(ab+ba) actually matches strings such as {"abba", "abbba", "abbbba"} where the b in ab can occure one or more times followed by ba reference
but since + is not currently implemented it treats it as a symbol

in current parser to generate your given FA the regex would be ((ab)|(ba))* to increase robusticity and making the parsing easier it is always contained in parenthesis.

here the input was ((ab)|(ba))* and generates a FA equivalent of the one you provided

there are certainly limitations in the current parser and tree generator requiring additional parenthesis i'l open issue for it

Do you want to transition the entire JS logic towards TS (adding type safety)?

Ideally yes