* adapt for structure change in gql backend (e.g. id -> rowId)
* display questions not rowId dependent anymore
* fixed calculation error if both, party and user, selected "skipped"
* fixed problems occuring when a candidate hasn't answered all questions (yet)
Also
* reorder graphQl queries: Always a query constant + update function
* use id instead of token (initials) to identify person in url
* Remove any party logo related sections since currently not needed
* Move "options" from data closer to actual code since it doesn't really belong to data
(data may be deleted in the future, anyway)
* add nodeId in gql queries wherever possible to avoid problems with the apollo cache
* add note about graphql schema import to README.md
With this commit two calculation errors are fixed
* the score in the case partyPosition = 'negative' while userPosition = 'neutral' shouldn't be MIN_POINTS but rather BASE_POINTS.
* the totalScoredPoints (now "totalMaxPoints") should be independent of any party-positions which it wasn't.
To minimize errors in this area in the future tests are added
which are based on the official Rechenmodel of the bpb.
To that end the score calculation logic was refactored
and moved from results.vue to scoring.js, too.
(cherry picked from commit 2d246fefbc4730ca5f7a4224325084a98f1c41f0)
It does not fetch anything yet.
It points to the graphql server on localhost, which is a hardcoded dev-mode.
Added config for GraphQL JS intellij plugin which inspects a "remote" graphql schema for better type hints in graphql queries in code
* improve imprint
* rename party -> person in route
* remove unnecessary components in about and partner
* fix email addresses
* remove most of the theses for easier manual testing (will be replaced by backendcalls in the future anyways)
* Remove Google analytics
* Remove cookies
* And the DSGVO banner
* Removed Social Media Connections
* Removed Cookie Consent stuff
* Removed Social Media related stuff in Datenschutzerklärung
* Remove xlsx data source
* Remove scripts to convert xlsx to json
* Convert data jsons into js files as a first step towards using a proper backend call for retrieval
* Remove dependencies related to xlsx
Christoph Lienhard
Willi Junga