Second change on MapVersion has no effect

Question

Closed this issue 6 years ago · 4 comments

Due to a bug in caching only the first change (i.e. un/rank or un/hide) is sent to the api. The ui shows the change but it is not stored in the db.

Answer 1 · 2018-05-13T10:56:16.000Z

Unfortunatly the fix leads to to an endless loop on production.

Answer 2 · 2018-05-14T10:53:49.000Z

Did you fix it?

Answer 3 · 2018-05-14T12:22:06.000Z

Yes. I delete the MapStruct cache now on every call to the API. Ugly, but seems to be the only way to get it working for now.

Answer 4 · 2018-05-14T21:22:40.000Z

well as long as it works 🔝