It feels like forking the source of the dependency would be a solution with much clearer path forward:
- you can add more "temporary" changes without inventing workarounds if needed.
- changes themselves can be added in a more declarative way (e.g. making two versions of the Item with a discriminator with its default value assigned to the old Item)
- you can document all deviations you needed if you switch to the newest canonical implementation
It requires access to that source, I didn't find this mentioned as an obstacle though.
binarybang@reddit
It feels like forking the source of the dependency would be a solution with much clearer path forward:
- you can add more "temporary" changes without inventing workarounds if needed.
- changes themselves can be added in a more declarative way (e.g. making two versions of the Item with a discriminator with its default value assigned to the old Item)
- you can document all deviations you needed if you switch to the newest canonical implementation
It requires access to that source, I didn't find this mentioned as an obstacle though.
Absolute_Enema@reddit
Fuck these so-called library "maintainers" that break their APIs every other release.