-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How does this project work? #1
Comments
btw I was requested by @conartist6 to do something with this website in iter-tools/regex#47 (comment) sooooo... yeah. we'll see what I can do if anything ❤ |
Here's some info from the readme:
|
I did some work on it the other day: #2 |
The main goal is to visualize the states that are active in the engine. The engine states form a tree structure, and each state has a matcher, which can be represented either as a regex literal or as a graph structure as presented in a traditional railroad diagram visualization. |
In terms of the matchers, those are defined in regex.ts. The |
My rather medicore attempt to print matchers that powers the current playground is here |
Are we OK with splitting things out into new components, or do we want to freeze the components as-is and just add more stuff to them? Should the new components (the ez one that I spotted is abstracting the main I note that some have function-style if this were moved to a new component, we could then add more stuff to the main |
Don't worry about offending me. If you think you can make anything better by changing how it's factored, where it lives, how it's documented, go right ahead! |
I've given you write perms on the repo, so feel free to put your work in a branch here. |
Sounds good! 👍 |
This is an issue tracking the documentation of how this website works. It's not necessarily a question per-se, but more of a "heyyyy let's document this stuff somewhere so we're all on the same page" issue.
The text was updated successfully, but these errors were encountered: