Closed nayr7 closed 1 year ago
may I ask why make a new PR when you could just rewrite the original PR instead?
I keep the other PR around for now in case I can fix/improve it, alongside a less messy git history in case https://github.com/krisppurg/dimscord/pull/101 is to be discarded in favor of this one
fixes https://github.com/krisppurg/dimscord/issues/112; alternative to https://github.com/krisppurg/dimscord/pull/101 using inheritance to allow referencing the current state of the user's
RestApi
from inside the library; is also likely to integrate well with the current design of https://github.com/krisppurg/dimscord/pull/110important info/considerations:
ctx
field, it will benil
if it didn't !DimscordObject
object that return from procedures do not have anil
field.DimscordObject.ctx
a public or private field for safety reasonstasks:
DimscordObject.ctx
is properly populated for every objects