handle case of no gradient

[ascibisz]

Problem

Right now, if you select "No Gradient" from the gradient dropdown, it fails to show up as the selected option in the input fields form.
Ticket

Solution

I did verify that the recipe JSON was being updated appropriately when the user selects "No Gradient", so all I needed to change was how we're determining which gradient option is selected.

There are two parts of the recipe JSON that are updated based on recipe selection, the gradient field that is set to membrane_gradient or nucleus_gradient etc, and the packing_mode field which is either set to random for the "No Gradient" case or gradient for all other cases. We hadn't been looking at packing_mode when determining what gradient option is selected, but that's the only way to determine if "No Gradient" is selected, so I added some logic to check this field as well.

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	20.14%	366 / 1817
🔵	Statements	20.14%	366 / 1817
🔵	Functions	41.37%	24 / 58
🔵	Branches	71.68%	81 / 113

File Coverage

File	Stmts	% Branch	% Funcs	% Lines	Uncovered Lines
Changed Files
src/utils/gradient.ts	0%	100%	100%	0%	10, 14-16, 29-32, 37-40, 43-47, 49, 51-52, 55, 58-59, 62-63, 65-66, 69-73, 75-76, 78-79, 81-87, 89-99

Generated in workflow #145

[github-actions]

PR Preview Action v1.6.2
Preview removed because the pull request was closed.
2025-11-12 21:16 UTC

[rugeli]

Played around on the preview site, No Gradient worked well, and packing_mode in the full data updated to random in real time!

Just noticed one mismatch: after selecting No Gradient, the gradient field in the full recipe data still shows the previously selected gradient(see screenshot). It'd be clearer to either update the field value to no_gradient or hide it altogether, whichever is simpler. Lmk what you think!

[interim17]

Non blocking question.

[ascibisz]

Played around on the preview site, No Gradient worked well, and packing_mode in the full data updated to random in real time!

Just noticed one mismatch: after selecting No Gradient, the gradient field in the full recipe data still shows the previously selected gradient(see screenshot). It'd be clearer to either update the field value to no_gradient or hide it altogether, whichever is simpler. Lmk what you think!

@rugeli I wasn't able to quickly find a solution that wouldn't throw an error in cellpack (setting gradient to no_gradient or null both threw errors), so I think let's investigate this further in a follow up ticket