Open hoeken opened 1 month ago
I like approach #1 - keep everything centrally located and keep the Psychic classes tidy without a lot of #ifdefs scattered around.
I like approach #1 - keep everything centrally located and keep the Psychic classes tidy without a lot of #ifdefs scattered around.
that's my goal, but for some exceptions it won't be possible... I.e. not worth redefining a whole decorator class if only 1 or 2 methods names have changd
@mathieucarbou if its just method names, or method parameters and not return values, we can add the compatibility functions directly to the class, no problem.
proposal from @mathieucarbou
Example:
content:
Note: I am not sure this is the right way to do it, it could also be done within the library classes, example right now I am trying to migrate by using that in a library:
So this is scoped to only my classes, but if this concept works, why not extending it globally and have Psychic provide a mapping class.