uptime-kuma/server/monitor-types
Frank Elsinga a9a1cf1353
Chore: General notification reformatting (#3182)
- I unified where in file the name of `NotificationProvider.name` is placed
- I made sure that all the providers adhere to the signature of `NotificationProvider.send()`
- I made sure that all the providers use `okMsg` if returning success messages directly from the function.
  Here a discussion should be had:
  Should this be refactored into a constant of `NotificationProvider`? I could imagine that `NotificationProvider.SENDING_SUCCESSFULL`  could be a suitable alternative.
- I made sure all providers have the URL they `POST`/`GET` to be extraced into a variable.
  => refactored this way due to Nelsons suggestion
2024-03-14 14:21:15 +01:00
..
dns.js Chore: Extracted the dns monitor to its own monitor-type (#3413) 2023-09-09 18:14:55 +08:00
monitor-type.js Chore: General notification reformatting (#3182) 2024-03-14 14:21:15 +01:00
mqtt.js MQTT monitor, set the MQTT clientId to make it easier in the MQTT broker to identify where the connections are coming from 2024-02-19 07:57:34 +01:00
real-browser-monitor-type.js Fix: missing await in getRemoteBrowser() (#4418) 2024-01-26 06:53:15 +08:00
tailscale-ping.js Merge branch '1.23.X' into merge 2024-01-03 02:10:01 +08:00