Closed huibertalblas closed 1 year ago
Yes, good point, I'll be sure to update the documentation! Thanks for bringing it up!
I might be looking in the wrong place (or it might have already been solved at some earlier point in time). But I do not see any actions with the same UUID. So I think this can be closed? Or did I miss anything @huibertalblas ?
Yes, it seems to be correct now! Thanks Bas
Type of bug
Describe the bug There seems to be an inconsistency in the sample data. The request sample under 'Trip' contains 2 load actions. Both actions have the same identifier, while their contents are different. (currently both have 'adcd2548-0c2c-4f39-8b4c-317dcbcb9c41')
To Reproduce Visit the example message under Trip
Expected behavior I would expect these two to load actions to have a different uuid. (currently both have 'adcd2548-0c2c-4f39-8b4c-317dcbcb9c41') Because, the get Actions endpoint only allows to return one Action for a given UUID. Therefore it seems not logical to have a duplicate identifier in one message.