Context: When a banking transaction can be linked to a konnector, the application offers to install the konnector to the user.
Correction(initial): The application must not offer konnectors for maintenance.
Originally, the only data source for retrieving information about konnectors was a JSON file (brands.json).
This could quickly lead to issues if the file was not strictly maintained, for example, whether a connector is in maintenance or not.
The solution here is to query the registry to retrieve all konnectors, filter the relevant information for the app, merge it with the JSON file, and save it in localStorage.
Since this information is not used only for React components, a Provider doesn't meet the requirements.
The total information represents approximately 23KB.
The solution of using the localforage library (already used in the app) was tested and rejected.
Transitioning to asynchronous operations would require a significant rethinking of many functional implementations.
Given the performance gains, the cost is too high.
As a result, we are sticking with synchronous operation but with up-to-date information about the konnectors and reducing our reliance on Redux.
In the near future, we hope to completely eliminate the need for the JSON file, but currently, the manifest files of the konnectors lack some information (such as contact or health).
### 🐛 Bug Fixes
* No chips for Konnectors under maintenance
### 🔧 Tech
* Retrieving connectors via the registry in addition to the JSON file
Context: When a banking transaction can be linked to a konnector, the application offers to install the konnector to the user.
Correction(initial): The application must not offer konnectors for maintenance.
Originally, the only data source for retrieving information about konnectors was a JSON file (
brands.json
). This could quickly lead to issues if the file was not strictly maintained, for example, whether a connector is in maintenance or not.The solution here is to query the registry to retrieve all konnectors, filter the relevant information for the app, merge it with the JSON file, and save it in localStorage. Since this information is not used only for React components, a Provider doesn't meet the requirements. The total information represents approximately 23KB.
The solution of using the
localforage
library (already used in the app) was tested and rejected. Transitioning to asynchronous operations would require a significant rethinking of many functional implementations. Given the performance gains, the cost is too high.As a result, we are sticking with synchronous operation but with up-to-date information about the konnectors and reducing our reliance on Redux.
In the near future, we hope to completely eliminate the need for the JSON file, but currently, the manifest files of the konnectors lack some information (such as
contact
orhealth
).