3 ms·
Why is the interface to a third party library not to be analyzed? I'll have to use it anyway so this way at least I can be more sure when calling the API what
by gempir 5y ago
Why is the interface to a third party library not to be analyzed?
I'll have to use it anyway so this way at least I can be more sure when calling the API what I need to pass or not.
I mean all of that applies to any library you ever import. You still have control over it in the means of commit hashes etc, so it won't randomly break. So it makes sense documenting the API for yourself if there is no documentation.
- bluGill 5y agoBecause you can't safely change it and also take the next upstream release. Either you live with whatever interface they give you, or you don't use it at all. Any change you make will be lost when they release an update with something else you need (perhaps a security fix). Now you can wrap the library if you want so that only the wrapper as to use the bad API. There are pros and cons to this.