Skip to content

Attributes not hard coded #22

@aavram

Description

@aavram

"You have attributes for your accessories (eg hue, saturation & luminence; or strength, armor, cost). Each of those probably has a valid value range. It would be appropriate to define these as "data", to avoid hard-coding. A good place to do that would be in an App model, like we have used in the last few labs." Right now we are hardcoding the names of the attributes in our CSV files. We have to change these to A1, A2 etc and put the values in App model.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions