Snog
Well-known member
I've got a couple of applications where I throw a more specific error for assertViewableThread.
The problem is that in order to do it, I basically have to run the entire assertViewableThread function to locate the exact reason for the error. And if it's not specific to my application, then return the parent function so as not to interfere with other add-ons that may extend the same function. That results in a lot of duplicate work.
For the life of me, I can't come up with a better way to do it, so I'm asking here.
What would be nice is if assertViewableThread returned the thread and any errors, that way $thread would already contain all of the info I need and if there wasn't a more specific error that could be thrown the extension could just return the thread and original error back into the mix. (HINT, HINT... @Chris D , @Mike )
The problem is that in order to do it, I basically have to run the entire assertViewableThread function to locate the exact reason for the error. And if it's not specific to my application, then return the parent function so as not to interfere with other add-ons that may extend the same function. That results in a lot of duplicate work.
For the life of me, I can't come up with a better way to do it, so I'm asking here.
What would be nice is if assertViewableThread returned the thread and any errors, that way $thread would already contain all of the info I need and if there wasn't a more specific error that could be thrown the extension could just return the thread and original error back into the mix. (HINT, HINT... @Chris D , @Mike )