Version number is repeated in code

[MrDeshaies]

The code defines the version number in way too many spots! Violation of the DRY principle ("Don't Repeat Yourself"). It makes it harder to increment the version number and risks having inconsistent version numbers between sections.

It's defined in:

1. package.json (incorrectly as 0.1.0)
2. wet.js versionIdentifier
3. store.ts in StoreOptions definition
4. survey-enfr.json in the HTML for welcome1
5. en.json (to support Results.vue)
6. fr.json (to support Results.vue)

As much as possible, a single source of truth should be identified and used. For example, Results.vue could use Survey.version instead of using the strings defined in en.json and fr.json.

[nschonni]

I think there might be a need for 2 version numbers:

1. The schema of the questions/response value files (4). EX: v0.8.0 we store departments as '001', and v0.9.0 the department is stored as a GUID.
2. The application could have an independent version number and be able to support multiple survey/response schemas, while bumping version as dependencies and libraries are bumped under the hood

6 definitely seems like too much 😄