story(sbb-pearl-chain): Refactor initial implementation about lyne-components HOT 2 OPEN

thank you for the specification!

my thoughts:

sbb-pearl-chain:

• all legs are cancelled: https://lyne-storybook.app.sbb.ch/?path=/story/timetable-sbb-pearl-chain--cancelled
• makes also sense for active state and cancelled -> If its cancelled there should be no active state (currently buggy)
• disableAnimation prop is missing: active state without pulse animation

sbb-pearl-chain-leg:

• is it like one leg = one dot (left side) and one line?
• should handle: first leg departure dot is bigger and last leg arrival dot is bigger (type: 'start-end' | 'stop')
• Business logic should be for the lines and dots: 'default' < 'past' < 'skipped' < 'disruption';

-Question about 'skipped': 'Skipped' can represent either the departure stop or the arrival stop. Should the leg siblings be aware of each skipped property, or should we implement it with two separate properties: 'departureSkipped' and 'arrivalSkipped'?

from lyne-components.

@kyubisation .
Thanks for writing the specification. It looks good for me in general. Some topics:

• Attributes on closing tags seem not really supported, but it's only a detail :)
• timer: The concept basically sound good, I'm just wondering if this is really a performance boost. As a drawback it could be that because all changes are handled with one event synchronous, it could also block/slowdown ui for a short time. This timer could also be used for the sbb-clock maybe.
• data-now: I think we should mention also, that for testing purposes it should be possible to set the current date by "data-now" (similar to other components).

@WalkingOS I think it's better to use arrivalSkipped and departureSkipped.

from lyne-components.