hone | research project from Princeton CS

You can use ESLint's no-useless-escape rule, which will suppress warnings when you use escape characters that don't change the string's meaning. Also see this question and its answers.

As a bit of extra info, - in a regex only has special meaning if it's inside of square brackets [ ] and otherwise does not need to be escaped. None of the instances in your regex appear to be inside such brackets, so it's safe to say the regex will work the same if you do decide to just remove the escape characters.

I'm pretty sure the issue the texture your rendering to is 8bits. Switch it to a floating point texture (RGBA32F) You'll need to check for and enable EXT_color_buffer_float and OES_texture_float_linear

You say it won't work on mobile but you're using WebGL2 which hasn't shipped on iPhone yet (2021/1/3). As for RGBA32F not being renderable on mobile you could try RGBA16F. You'll have to check for and enable the corresponding extensions, EXT_color_buffer_half_float and OES_texture_half_float_linear. Your current code is not checking that the extensions actually exist (I'm assuming that was just to keep the code minimal)

The corruption is that your circle calculation draws alpha < 0 outside the circle but inside the quad. Before that was getting clipped to 0 because of the texture format but now with floating point textures it's not so it affects other circles.

Either discard if c <= 0 or clamp so it doesn't go below 0.

Note: you might find coloring faster and more flexible using a ramp texture. example, example2

Also note: It would have been nice if you'd created a more minimal repo. There's no need for the animation to show either issue

Something else to point out, maybe you already knew this, but, the circle calculation

createItem (name it upsertItem if you wish) mutation resolver can insert or update (BE, resolver implementation/storage/DB related decision) with or without strict/explicit input type definitions (required for create, optional for update)

... tenants can have different input types (fields amount) for the same mutation

... in wp-graphql (WordPress) it's even role based - different introspection results, different args for fields, different mutations available ... but it's from dynamic, non-persistent/stateless php character

You can just limit fields usage (per tenant) or type matching (required/not required) in some validation 'layer' inside resolver or in middleware just by throwing errors (when input doesn't match specific usage/tenant - f.e. return 'required error' for some field while all fields in type definitions are optional). When introspection query is blocked (on production) then it's just a documentation problem (not self-describing).

if the target entity to upsert is a Person with an ID, and First, and Last names, (ID and Last are required)

ID can't be required here ...

UpsertPersonInput with all (ID, First, Last) optional ...

For create: upsertPerson( $input: UpsertPersonInput) {.. with variables required (by validation rules) for creation (First: "some", Last: "Name")

... ID unknown here, created and returned as result

...no ID provided then assuming 'creation mode'

For update: query the same but when provided input variable with ID prop validation works in 'update mode' (at least one other variable - input prop - required, f.e. Last ... or other additional validation rules)

... while only input.ID prop provided > throw some "no required 'First' passed in input arg" (any field) Error ... as it would in separate update mutation and its input type.

From the documentation:

step_interact can create interactions between variables. It is primarily intended for numeric data; categorical variables should probably be converted to dummy variables using step_dummy() prior to being used for interactions.

step_dummy(all_nominal()) turned the variable smoker into smoker_yes. Below, you'll see that I just changed the name of smoker in the interaction term to smoker_yes.

One solution could be to have a submit button that you hide by default (on the first tab) and show once you go to the second (or last if you add more). This way you won't have to change the innerHTML on any element and just toggle a class. Something like that could look like:

There's a lot to be changed. Please look at the CSS code in the snippet below. The most important things: No floats, inline-block vs. inline display, no fixed width for the ul, no auto margins, text-align: center for the container and others:

Unless you are actually using elemen for anything else than printing this pattern, I suggest dropping it and print the pattern directly.

Example:

You can instead use the values of the enum, rather than the keys as you have here.

To do this, you extract object values via T[keyof T] - where T is your enum type (typeof SOME_STRING_ENUM).

This gives you pretty much as you had written the second example:

Hey ZioPaperone welcome to the JS World :-)

First of all I would recommend to wrap you logic into functions, eg