You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Every CCS and the CDS support additional properties beyond the spec. The two scoreboard_type values also essentially add properties to various objects (e.g. penalty_time or scoreboard row elements).
It doesn't make sense to put the CCS/CDS additions in the spec so each are documented differently today. If we had a couple more scoreboard_types/scoring algorithms these would quickly become unwieldy, or we might not want to put all of them directly in the core spec. It's also hard to scan and see what properties something like pass-fail adds.
Does it make sense to have a 'standard pattern' for how spec additions/extensions (especially ones that affect multiple objects) are documented? We could start this for scoreboard_type as part of the spec, which would give a template for how external documentation should do it.
The text was updated successfully, but these errors were encountered:
Discussion topic for future meeting:
Every CCS and the CDS support additional properties beyond the spec. The two scoreboard_type values also essentially add properties to various objects (e.g. penalty_time or scoreboard row elements).
It doesn't make sense to put the CCS/CDS additions in the spec so each are documented differently today. If we had a couple more scoreboard_types/scoring algorithms these would quickly become unwieldy, or we might not want to put all of them directly in the core spec. It's also hard to scan and see what properties something like pass-fail adds.
Does it make sense to have a 'standard pattern' for how spec additions/extensions (especially ones that affect multiple objects) are documented? We could start this for scoreboard_type as part of the spec, which would give a template for how external documentation should do it.
The text was updated successfully, but these errors were encountered: