Right now we're using the special case that seed yields have the string "Yield" somewhere in them. It'd be much cleaner to have a 'yield' section in the json, but that makes the csv reader pretty much worthless without some reworking.
This issue isn't scheduled in a sprint, but it would be nice to be able to structure the seed data sanely (as described in a PR review comment in #82) but still edit it easily.
Right now we're using the special case that seed yields have the string "Yield" somewhere in them. It'd be much cleaner to have a 'yield' section in the json, but that makes the csv reader pretty much worthless without some reworking.
This issue isn't scheduled in a sprint, but it would be nice to be able to structure the seed data sanely (as described in a PR review comment in #82) but still edit it easily.