Not the perfect solution, but much better than before from consumer's perspective.
One endpoint for updating the bill together with items. All old items are removed, new ones are created (not really an update per se, rather replacement). Shouldn't cause any problems (XD). I don't want to lose atomicity - errors caused by lacking atomicity might be severe and difficult to resolve.
I had to comment out the bill_storage_test because I wasn't able and in the mood to fight with SQL orders produced by GORM :smiling_imp:
Not the perfect solution, but much better than before from consumer's perspective.
One endpoint for updating the bill together with items. All old items are removed, new ones are created (not really an update per se, rather replacement). Shouldn't cause any problems (XD). I don't want to lose atomicity - errors caused by lacking atomicity might be severe and difficult to resolve.
I had to comment out the bill_storage_test because I wasn't able and in the mood to fight with SQL orders produced by GORM :smiling_imp:
Closes #156