Fix: Browse and Search types
Hi,
For at least the Search and Browse apis, there were a LOT of usage of Partial<...> when in fact almost all fields seem to always be present. I checked the api responses and also checked the online api documentation and these are the changes I feel pretty confident with. I hope you can consider at least most of these changes. I look forward to any feedback as well.
Instead of using Partial I tried to make only select fields optional using the ?: syntax. Also I split some interfaces into separate more specific ones to be able to provide better typings in all scenarios.
Hey @xkr47 , thanks for your contribution! We will review and get these merged
@xkr47 my apologies for the delay. We looked into this PR and it's looking good. Since these are breaking (in terms of TS) changes, we are going to hold off merging this PR until our next major release which will be after BF period. If you urgently need these changes, let me know and we can look for alternatives to support you
Yeah makes sense. No worries, we are going to use my PR branch directly in our project until then so december-january timeline is fine with us.