Web SDK Refactor: Operation Repo Rework

[fadi-george]

Description

This is the start of the Web SDK rework which can be read here.

With the goal of solving issues with having correct commands (addTag) apply to the correct user (login) in the right order.

This pr focuses on porting on the Android SDK OperationRepo Class to typescript.

1 Line Summary

• Refactor OperationRepo to be more similar to Android SDK implementation

Details

• Ports OperationRepo code from Android SDK to typescript
• Adds new uuid package for setting the operation ids
• Avoided using LoopWaiterMessage , WaiterWithValue, Waiters as it doesnt seem needed but I may revisit this
• Likewise did not implement that relied on waiters/wake logic like forceExecuteOperations, waitForNewOperationAndExecutionInterval, delayForPostCreate, delay (already a separate util) methods
• Did not implement use configModelStore and time (since we have Date) in the constructor. The configModelStore holds some constants that I extracted out but can revisit implementing in later prs
• Skipped some tests since operation repo caused them to break

Systems Affected

• WebSDK
• Backend
• Dashboard

Validation

Tests

Info

Checklist

• All the automated tests pass or I explained why that is not possible
• I have personally tested this on my machine or explained why that is not possible
• I have included test coverage for these changes or explained why they are not needed

Programming Checklist
Interfaces:

• Don't use default export
• New interfaces are in model files

Functions:

• Don't use default export
• All function signatures have return types
• Helpers should not access any data but rather be given the data to operate on.

Typescript:

• No Typescript warnings
• Avoid silencing null/undefined warnings with the exclamation point

Other:

• Iteration: refrain from using elem of array syntax. Prefer forEach or use map
• Avoid using global OneSignal accessor for context if possible. Instead, we can pass it to function/constructor so that we don't call OneSignal.context

Screenshots

Info

Checklist

• I have included screenshots/recordings of the intended results or explained why they are not needed

---

Related Tickets

---

---

This change is 

---

• To see the specific tasks where the Asana app for GitHub is being used, see below:
  • https://app.asana.com/0/0/1208801496090558
  • https://app.asana.com/0/0/1209953504584238

[sherwinski]

Let's add a comment to refer to the NewRecordsState file in the android SDK. Either that, or copy the source-level comments from the file.

I would recommend doing this for each of the classes/functions you've defined below as makes it easier to understand the individual components more easily.

[fadi-george]

I'll add references to those.

[sherwinski]

We should update this comment if we're not using waiters

[fadi-george]

Updated

[sherwinski]

same comment here about clarity

[fadi-george]

Updated