payload | Built with React + TypeScript , Payload | Content Management System library

I don't see where old.otp is being set in the SendOTP class, that's probably why it's None. Should be something like this:

We're looking in to the same issue currently and it seems apple are disabling the old binary interface which push sharp uses.

https://developer.apple.com/news/?id=c88acm2b

pushsharp has it on the roadmap to support the new interface but not completed yet.

Found this library which seems easy enough to use as a solution. hope this helps.

https://github.com/alexalok/dotAPNS

It looks like you have problem in mapStateToProps

You are telling your server, you are sending JSON data, but the request body is not a JSON string but a url-encoded string (because that's the default behaviour of $.ajax() when you pass an object as data).

Use JSON.stringify, to pass a correct JSON body

This is not consumed by json_normalize directly (after my tries). Since the number of BUY and SELL are different, and these record do not neccessarily should match each other (located on a same row), suggestions is to split into two dataframes and then concatenate.

Azure Cosmos db is only supporting Unicode or ASCII in x-ms-documentdb-partitionkey while github.com/vippsas/go-cosmosdb package is using json.Marshal which internally transforms Unicode to Chinese characters automatically.

The only way to solve it is using English as partition key when creating documents.

Judging from the curry api, curry a function either calls the function if all its parameters are provided or returns a new function that requires only a subset of parameters if some are provided.

For example in your code

Assign function for add_LicenceComponent of sharedService instead returning void.

Another thing is your getting TypeError because of service not initialised while trying to access it in constructor. Move it to ngOnInit() and do check do whether you added them in providers

You need to do some modifications in your component code like below,

You should deffinitely use a cloud function to update the stock. Create a function onCreate and onDelete functions trigger. If users can change data you would also need to onWrite function trigger.

Depending on the amount of data you have you woould need to create a custom queue system to update the stock. Belive me! It took me almost 2 years to figure out to solve this. I have even spoken with the Firebase engeeners at the last Firebase Summit in Madrid.

Usualy you would use a transaction to update the state. I would recommend you to do so if you don't have to much data to store.

In my case the amount of data was so large that those transactions would randomly fail so the stock wasn't correct at all. You can see my StackOverflow answer here. The first time I tought I had an answer. You know it took me years to solve this because I asked the same question on a Firebase Summit in Amsterdam. I asked one of the Engeeners who worked on the Realtime Database before they went to Google.

There is a solution to store the stock in chunks but even that would cause random errors with our data. Each time we improved our solution the random errors reduced but still remained.

The solution we are still using is to have a custom queue and work each change one by one. The downside of this is that it takes some time to calculate a lot of data changes but it is 100% acurate.

Just in case we still have a "recalculator" who recalculates one day again and checks if everything worked as it should.

Sorry for the long aswer. For me it looks like you are building a similar system like we have. If you plan to create a warehouse management system like we did I would rather point you to the right direction.

In the end it depends on the amount of data you have and how often or fast you change it.