feat(es_extended): Extra callback functions #1505
Conversation
|
I don't see the point of this. ESX already throws an error if a resource attempts to access an invalid callback. This just promotes people calling Third party resources can check if their dependencies are started and just assume that all expected callbacks are registered. We are already letting them know if they are not ^^ |
I agree with Kenshin on this one, there is 0 usecase for it and litterly no one ever requested a functionality like this |
| ---@return table | nil | ||
| function ESX.GetClientCallbackInfo(eventName) | ||
| return Callbacks.storage[eventName] | ||
| end |
There was a problem hiding this comment.
This doesn't need to be a thing
| ---@return table | nil | ||
| function ESX.GetServerCallbackInfo(eventName) | ||
| return Callbacks.storage[eventName] | ||
| end |
There was a problem hiding this comment.
This doesn't need to be a thing
Introduces 4 new functions:
ESX.DoesClientCallbackExistESX.GetClientCallbackInfoESX.DoesServerCallbackExistESX.GetServerCallbackInfo