As a user
I want to be able to specify which columns correspond to which gypsy variables
So that I can run gypsy without renaming the fields in my data
Currently, the whole system assumes column names are fixed to our constants, e.g. here
This is inconvenient for users as described in user story above.
We can make it configurable by indexing the data using global variables, e.g.
Configuring a bunch of module level constants (singletons) is difficult and dangerous. this is a good place to use a class with getters and setters as here for example
This will store all the columns as properties on a class so we can do
data[col_config.black_spruce_age]
And those properties will be protected from modification by overriding the setter as shown in the link above
the drawback here is that this col_config class must be used anywhere we index the data. it may not be intuitive for new developers
Currently, the whole system assumes column names are fixed to our constants, e.g. here
This is inconvenient for users as described in user story above.
We can make it configurable by indexing the data using global variables, e.g.
Configuring a bunch of module level constants (singletons) is difficult and dangerous. this is a good place to use a class with getters and setters as here for example
This will store all the columns as properties on a class so we can do
And those properties will be protected from modification by overriding the setter as shown in the link above
the drawback here is that this
col_configclass must be used anywhere we index the data. it may not be intuitive for new developers