[2.0]: `code` should probably not be reserved by p5

[quinton-ashley]

Most appropriate sub-area of p5.js?

• Accessibility
• Color
• Core/Environment/Rendering
• Data
• DOM
• Events
• Image
• IO
• Math
• Typography
• Utilities
• WebGL
• Build process
• Unit testing
• Internationalization
• Friendly errors
• Other (specify if possible)

p5.js version

2.0.1

Web browser and version

No response

Operating system

No response

Steps to reproduce this

In p5 v2 there's a prop on p5.prototype called code, though I'm hoping this is a typo and should be keyCode, as it's only declared but never used.

Will workaround by running delete p5.prototype.code inside p5play.

[quinton-ashley]

@davepagurek Is p5.js v2 reserving code a mistake or is it reserved for some future use?

[davepagurek]

This is intentional, keyCode is deprecated and replaced with key and code in keyboard events in vanilla js, and p5 2.0 follows suit. Docs being added here: #7902