![[logo]](https://ibboard.co.uk/warfoundry/images/logo.png){kind=logo}
WarFoundry - Development#52 closed enhancement (fixed)
Add requirements to Schemas
| Reported by: | ibboard | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | WarFoundry API 0.2 |
| Component: | WarFoundry-API | Version: | Unknown or N/A |
| Keywords: | Cc: | ||
| Blocked By: | #347, #348, #349 | Blocking: | #27, #29, #351 |
Description
Requirements are optional (races don't need to define any special requirements) but useful. They need to be added to the schema so that they can be defined and enforced.
Change History (14)
comment:1 Changed 11 years ago by
| Blocking: | 27 added |
|---|
comment:2 Changed 11 years ago by
| Blocking: | 29 added |
|---|
comment:3 Changed 11 years ago by
| Owner: | ibboard deleted |
|---|
comment:4 Changed 10 years ago by
| Blocking: | 57 added |
|---|
comment:5 Changed 10 years ago by
| Status: | new → confirmed |
|---|
Move tickets to new "confirmed" status to show that they've been checked
comment:5 Changed 9 years ago by
| Milestone: | WarFoundry 0.2 → WarFoundry API 0.2 |
|---|
Separate API milestone from UI milestone
comment:6 Changed 9 years ago by
| Blocking: | 57 removed |
|---|
(In #57) Ticket doesn't make sense any more - we're defining the spec as we go and relying on backward/forward compatibility so there is no "complete" to load.
comment:7 Changed 9 years ago by
| Blocked By: | 347 added |
|---|
comment:8 Changed 9 years ago by
| Blocked By: | 348 added |
|---|
comment:9 Changed 9 years ago by
| Blocked By: | 349 added |
|---|
comment:11 Changed 9 years ago by
| Blocked By: | 349 added |
|---|
comment:12 Changed 9 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | confirmed → closed |
| Version: | → Unknown or N/A |
As of r936 we're going to use a single (extensible) format that uses a string of data. It isn't perfect, but it is the most generic method available. XML can identify the requirement type by attribute value, other formats can use other methods, and a factory can then pass the string without needing to know about the data source (in theory).
comment:13 Changed 9 years ago by
| Blocking: | 351 added |
|---|
Remove owner so that the team can more easily see bugs. Using default owners seems good at first but is bad practice when a team can be working on any part of the project.