mateenbagheri
commented
2 weeks ago Note on what state this task is at: There has been a long time since an update has been pushed to memorabilia. Here what has been achieved during this hiatus.
- Created our own Data type for memorabilia
- Write tests for mentioned data type
- Write get and set features without tests. There yet tests to be written for this to make sure that things are working fine.
What is left to be done:
- Document the process. For example we need to document why we created our own data type system for memorabilia.
- Write extensive tests for get and set functionalities.
- Research on how to test concurrent situations. The problem is that most concurrent situations occur when ordering of events is not as predicted. These errors occur some and not all the times. Yet I want to have strict CI in the future that catches any bugs including concurrency bugs. How can I achieve this?
This will be done alongside #5. This task also comes along with task of building a secure data structure for handling in memory allocations. As of now, I plan this project to be using an in memory map for handling data but there are going to be challenges that need to be addressed as going forward. One of the main challenges is datatype support for memorabilia. The other main challenge is persisting the data in the further future. Currently, the structure has to be robust enough to support future changes in store structure. Therefore using a repository pattern is a must.