-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Fixed Issue #978 #1015
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
Fixed Issue #978 #1015
Conversation
https://editor.p5js.org/Janglee123/sketches/z5DUgwwjy All keywords have highlighted now. |
this definitely improves the issue. i've noticed that they keywords in p5.dom and p5.sound are not highlighted, and i'd like to add those too. |
@catarak Cool I'll add those as well. If you have a list, my work will get a bit easier. |
I just opened processing/p5.js#3666 to address getting a list. I was trying to remember how I originally got the list of keywords, and I couldn't. The only thing I can think of is that I got it from the now deprecated p5.js desktop editor. |
i think the way to approach this is going to be to parse the data.json file that gets updated with every p5.js release |
The 'name' key? Like extract all values with key 'name' and store them as keywords? |
you'll also need to check |
@catarak I have a doubt! Should I include all constants with itemtype=property? Because that's including some really strange variables like x,y and z. |
looking over data.json, i think for itemType=property, you also need to look at the class. for example, x, y, and z, are properties of p5.Vector, and the class for them is |
@catarak I have added them. Just check if some methods or variables have to be removed? |
this is working great for me, and the dom/sound variables are included! woohoo! |
I have verified that this pull request:
npm run lint
)@catarak views?