Updated namespace with keyInfo item; added 'anyOption' to records

[hudaif747]

Description

Related Issues

Design Decisions

Performance & Quality

Checklist

I, the author of this PR checked the following requirements for good software quality:

• The code is properly formatted (I ran the formatter)
• The code is written with our software quality standards (I ran the linter)
• The code is written using our code style
• Extensive in source documentation has been added
• Unit and/or integration tests have been added
• All texts have been internationalized with at least the following languages:
  • English
  • German
• I tried addressing all new accessibility problems displayed in the console and documented if they can't be fixed
• I attached performance measurements to prevent performance degradation
• I added the changes to the next release section of the changelog

I, the reviewer checked the following things:

• I ran the software once and tried all new and related functionality to this PR
• I looked at all new and changed lines of code and commented on possible problems
• I read the added documentation and checked if it is understandable and clear
• I checked the added tests for completeness
• I checked the internationalized strings for spelling errors
• I checked the performance metrics for problems or unexplained degradation
• I checked that the changes are noted in the changelog

[NXXR]

👍
the Prettier Job failed

check if running npm run format makes things better or worse.
If worse you can either remove the leading comments in the maps since I assume they are the reason why the formatter is unhappy. Otherwise, you can probably also exclude this file from the formatter somehow.

[NXXR]

I also checked the differences between feature/pandemos-datasocket-preprocessing and feature/pandemos there are barely any changes.
The files were moved and the KeyInfo-Stuff was moved from the datasocket to the types file.

Other than that the only major change is that the raw data is served as an array not a crossfilter anymore, and therefore an additional large crossfilter object with the agent and location infos merged into the trips is provided for @Pawandeep-Kaur-Betz statistics and @apoorvakay might also use this object to filter and display the map (if she doesn't use the raw trip and location array and filter based on the PandemosFilterSlice in the store)

You can check the datasocket code if there are any comments or todos that need fixing but I think most of it was optional for now.
If all looks good you can also merge the feature/pandemos-datasocket-preprocessing branch into the feature/pandemos branch.
make sure to let the others know as they probably need to pull the changes into their branches and modify their code accordingly.

[github-actions]

Test Results

0 tests  ±0   0 ✅ ±0   0s ⏱️ ±0s
0 suites ±0   0 💤 ±0 
0 files   ±0   0 ❌ ±0 

Results for commit 888ed18. ± Comparison against base commit de002a0.

♻️ This comment has been updated with latest results.

[NXXR]

Did you find the issue with the formatter @hudaif747 ?

[hudaif747]

Did you find the issue with the formatter @hudaif747 ?

The formatter fixed single qoutes in the pandemos.ts it did not mess with the rest of the file. The lint fix suggested to add disable comment for namespace and also to remove non-null assertions in the PandemosContext.tsx