Closed dror-wing closed 8 months ago
Thanks for letting us know about this issue and your use case. Thank you for the xkcd. 😊
There was some discussion of the possibility of breaking in #300. We wanted to add a field to this project, which sounds like a minor version bump. However, maybe when a public interface is a tuple, there's no way to lengthen the tuple (nor shorten it) without it being a breaking change?
In the meantime, for anybody encountering this issue, to work around: directly reference the fields you're interested in.
Ouch, this break cases like:
'.'.join(part for part in ext[-2:] if part)
I upgraded to direct field referencing but I would consider this a breaking change.
(subdomain, domain, suffix, is_private)
return type. Lesson learned that increasing the length of a tuple should be a breaking change.ext[-2:]
will no longer work at all. Use (ext.domain, ext.suffix)
instead.
Our production code broke after upgrading to version 3.6.0 because of the following line:
We were expecting a breaking change would reflect in a major version bump as per the semver spec.
Thank you