If you have a project that's missing a "private" field (e.g. :version) then you'll start to accrue "nil" values in your project when you run prosjekt-setup-save() is run. This is because the call to (assoc key prosjekt-proj) spits out nils for the missing field.
We should address this. One option is to associated a default value with each private field that we stitch back in. The other - probably better - approach is to no stitch in any nil values.
FWIW, this bug does actually break the project, it just makes it grow by a nil each time you save. It's annoying and definitely a defect, but not critical.
If you have a project that's missing a "private" field (e.g. :version) then you'll start to accrue "nil" values in your project when you run prosjekt-setup-save() is run. This is because the call to (assoc key prosjekt-proj) spits out nils for the missing field.
We should address this. One option is to associated a default value with each private field that we stitch back in. The other - probably better - approach is to no stitch in any nil values.