[SiteRelEnby]

Brings the slider custom field type across from the server and the web app, and fixes the way this client treats a field type it does not recognise.

Slider fields

Two kinds, as the server defines them:

• Labeled: a fixed 0 to 100 between two words of your choosing, read as a percentage. "Drained" to "Wired".
• Numeric: a quantity in the owner's own range, with a step and a unit. "172.5 cm".

Either can paint a gradient across the track, picked from the same nine named ones the web card offers or built from your own colours using the colour picker the app already uses for member and tag colours.

Settings gets the whole setup with a live preview. The member editor gets a draggable track with the reading beside it and a tap to clear. A member's profile shows the reading. The reading is produced the same way the server produces it for a public profile, so a slider reads the same string wherever it turns up.

Three things worth flagging in review

Options are replaced, not merged. A slider's options are the one body this client sends that the server rebuilds from scratch rather than patching. A key left out is a key reset to its default, which is how a label, a unit or a gradient gets cleared, since there is no explicit null to send. That makes Moshi's omit-nulls exactly right here and makes it the opposite of the PATCH bodies next door. Because the difference is invisible at the data class, the wire shape is pinned at the JSON instead: a stray choices riding along on a slider would 422 the whole save.

The track is drawn rather than left to Material. A gradient cannot be expressed as a track colour, so a gradient slider would otherwise be a different shape from one without, and the two sit next to each other in the same member's field list. This was visibly wrong on device before the fix. Same bar either way now, and the same bar the read-only readout and the settings preview draw.

Float noise no longer reaches stored values. Material's slider is Float-valued, and dragging to the 85 stop on a 0 to 100 track stored 85.00000762939453 while the reading said "85%". Values now snap to the step grid, or to the two decimals the reading shows, so the number stored is the number the user was shown. The web stores a clean 85, so this was a real divergence.

Unknown field types

A field whose type the server knows and this build does not showed "Unknown field type" in red where its value should be. That hid what a member had actually put there behind something that looks like a fault, and it is why a slider field on an older build looks broken rather than merely unsupported.

The API asks clients to treat an unknown type as text, so it now shows the value with a note to update the app. No editor is offered, deliberately: guessing at one risks writing a string into a field the server validates as something else.

Note this differs from the web, which falls through to a plain text input for a type it does not know. Happy to match that instead if you would rather the two agree, but read-only looked like the safer of the two for a client that cannot know the value's shape.

Also in here

The field type names on this screen now match the web card's ("Yes/No", "Select (single)", "Multi-select") rather than capitalising the API value, so the list, the dropdown and the edit dialog agree with the other client. Small user-visible change beyond the slider work, so calling it out.

Verification

Tests: 25 new, covering the options contract, the readings, the defensive resolution of a partial options object, the wire shape in both directions, which types may carry options, the bounds the server would refuse, gradient preset matching, and the float-noise regression with the exact value observed on device. I checked the wire test fails when the labeled/numeric split is removed.

Checked against a server with the type, from the phone:

• Creating a labeled slider stores the canonical options, gradient and all.
• Renaming the field leaves its shape intact.
• Clearing a label and the gradient clears both and leaves the other label alone.
• A dragged value lands as a clean number, and the profile shows the reading.
• Re-opening the edit dialog recognises the stored colours as their named gradient.