discourse/app/assets/javascripts/admin/addon/components/webhook-event-chooser.hbs

<label class="hook-event">
  <Input @type="checkbox" @checked={{this.enabled}} name="event-choice" />
  {{this.details}}
</label>
DEV: Modernize the remaining admin-webhooks parts (#19438) 2022-12-13 20:32:34 +08:00			`<label class="hook-event">`
DEV: Admin webhooks interface issues (#19360) 1. The events table had broken styling, making each row overflow 2. It had confusing routes: `/:id` for "edit" and `/:id/events` for "show" (now it's `/:id/edit` and `/:id` respectively) 3. There previously was an unused backend action (`#edit`) - now it is used (and `web_hooks/:id/events` route has been removed) 4. There was outdated/misplaced/duplicated CSS 5. And more 2022-12-13 08:53:08 +08:00			`<Input @type="checkbox" @checked={{this.enabled}} name="event-choice" />`
FEATURE: granular webhooks (#23070) Before this change, webhooks could be only configured for specific groups like for example, all topic events. We would like to have more granular control like for example topic_created or topic_destroyed. Test are failing because plugins changed has to be merged as well: discourse/discourse-assign#498 discourse/discourse-solved#248 discourse/discourse-topic-voting#159 2023-10-09 11:35:31 +08:00			`{{this.details}}`
DEV: Admin webhooks interface issues (#19360) 1. The events table had broken styling, making each row overflow 2. It had confusing routes: `/:id` for "edit" and `/:id/events` for "show" (now it's `/:id/edit` and `/:id` respectively) 3. There previously was an unused backend action (`#edit`) - now it is used (and `web_hooks/:id/events` route has been removed) 4. There was outdated/misplaced/duplicated CSS 5. And more 2022-12-13 08:53:08 +08:00			`</label>`