Opened 10 years ago

Closed 10 years ago

Last modified 9 years ago

#289 closed task (released)

Double-check extensibility where sets of values are allowed

Reported by: ibboard Owned by: ibboard
Priority: major Milestone: WarFoundry 0.1
Component: WarFoundry-API Version: Unknown or N/A
Keywords: schema extensability Cc:
Blocked By: Blocking:

Description

While looking at #279 I realised that the old schema isn't actually fully extensible because the schema requires one of the pre-defined limit elements, but we need to add an extra "composition" one. ArmourType may also need to be reworked for similar reasons.

Change History (6)

comment:1 Changed 10 years ago by ibboard

(In r582) Re #289: Double-check extensibility where sets of values are allowed

  • Remove ArmourType and all usage as it needs rebuilding from scratch to be extensible and isn't widely used yet

comment:2 Changed 10 years ago by ibboard

Owner: set to ibboard
Status: new → accepted

comment:3 Changed 10 years ago by ibboard

(In r583) Re #289: Double-check extensibility where sets of values are allowed

  • Allow other tags in the choice of elements for a limit

comment:4 Changed 10 years ago by ibboard

(In r584) Re #289: Double-check extensibility where sets of values are allowed

  • Add extra elements to sample racex file

comment:5 Changed 10 years ago by ibboard

Resolution: → fixed
Status: accepted → closed

Everything else seems sensible. There are no other choices and the only enumerations are ones that make boolean options a little nicer to read and explicit (e.g. "roundDirection" of up/down rather than "roundUp" as a boolean where false means down rather than not rounding).

comment:6 Changed 9 years ago by ibboard

Resolution: fixed → released

Retro-actively tag RC1 releases as released

Note: See TracTickets for help on using tickets.