[SOLVED] Webhook type event name change

[peterstarling]

I have…

• [x] Read the following guideline: https://docs.squidex.io/01-getting-started/installation/troubleshooting-and-support. I understand that my support request might get deleted if I do not follow the guideline.

I’m submitting a…

• [x] Regression (a behavior that stopped working in a new release)
• [ ] Bug report
• [ ] Performance issue
• [ ] Documentation issue or request

Current behavior

This is what the list of events look like in our hub:

As you can see recently the name (type) of the event has changed. This is not acceptable - it broke our infrastructure that relies on the field

Expected behavior

The names should be consistent and no such breaking change should be introduced without previous warnings

Minimal reproduction of the problem

Environment

• [ ] Self hosted with docker
• [ ] Self hosted with IIS
• [ ] Self hosted with other version
• [x] Cloud version

Version: [VERSION]

Browser:

• [ ] Chrome (desktop)
• [ ] Chrome (Android)
• [ ] Chrome (iOS)
• [ ] Firefox
• [ ] Safari (desktop)
• [ ] Safari (iOS)
• [ ] IE
• [ ] Edge

Others:

Can we ask for a rollback?

[Sebastian]

I am sorry, this event type was mainly used for debugging and the log UI. I am not aware that you have used it for your webhook. I will revert this change.

[peterstarling]

Thanks @Sebastian.

Yes, I think this is the piece of data in the payload that helps us identify the type of the received message (create/update). Do you think there is a field that is a better fit for it?

[Sebastian]

I will revert it anyway. It is in the build pipeline right now. You can also use the schema and the general type field.