Skip to content
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

Figure out productive categories to be auto-detected from source code #74

Open
lpmi-13 opened this issue Sep 12, 2020 · 0 comments
Open

Comments

@lpmi-13
Copy link
Contributor

lpmi-13 commented Sep 12, 2020

So in thinking about how to extract examples of different things from source code for learners to work with (what I did in https://examplar-code.netlify.app, but WAY more fleshed out), saw a list of things from javascript that would be cool to isolate and extract.

Screenshot_20200912-135856_Twitter

And obviously variables are easy to grab via abstract syntax tree parsing, and things like destructuring and rest/spread should be possible to filter out, since the forms are fairly predictable (actually, maybe the AST parsers can already just find these...haven't looked too close yet)...

But how to deal with stuff like state/immutability?

So the idea is basically to just compile on how to deal with these...or even which ones are worth trying to isolate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant