Discussion: Should WheelSlotRotation's slotNumber be stepped?

[Breina]

Currently on the capability types docs: https://github.com/OpenLightingProject/open-fixture-library/blob/master/docs/capability-types.md

Seems like it's either speed or angle that are being appended with Start and End. Semantically it doesn't make sense to have a range of slotNumber. The JSON schema does allow slotNumberStart and slotNumberEnd on WheelSlotRotation, however I confirmed that no current fixtures use these fields.

This leaves me confused. Should "🐾 must be stepped" be added to slotNumber?

[FloEdelmann]

Hmm that does makes sense. However, I guess it's currently the way it is because is either stepped in all capability types or not stepped in all capability types:

open-fixture-library/lib/model/Capability.js

Line 10 in e58e475

const START_END_ENTITIES = [`speed`, `duration`, `time`, `brightness`, `slotNumber`, `angle`, `horizontalAngle`, `verticalAngle`, `colorTemperature`, `soundSensitivity`, `shakeAngle`, `shakeSpeed`, `distance`, `openPercent`, `frostIntensity`, `insertion`, `fogOutput`, `parameter`];

I figure we could change that, but I don't really think it's worth the effort. But a PR would be welcome 🙂

[Breina]

Ah I see. I'm not comfortable in adding an edge case to JS, so I'll update the docs to make this clearer. :)