You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For context I'm using this client to interact with an implementation of the dataverse project. The issue is that there are some differencies between the basic dataverse native API and this implementation. There are some aditional optional or mandatory fields. For this reason I wanted to extend a few classes to add these. But this has proven to be quite difficult.
The text was updated successfully, but these errors were encountered:
Hi Gaby
Sure, feel free to submit a pr with the changes you'd like to see. These
methods could be made extensible, there just wasn't a use case for this
before.
Best wishes Richard
Hi,
Thanks for you quick answer!
I have forked the project and am currently working on these changes.
It might take a few weeks before I'm sure I have changed all I need.
I might also submit an other pr for an issue I have encountered with the "metadataLanguage" field on Dataverses with multiple languages.
Is there a particular reason why a lot of methods are private rather than simply protected or even public?
For example in this file : https://github.com/IQSS/dataverse-client-java/blob/44e37e12d015105afef26df63db4949b538ce2b4/src/main/java/com/researchspace/dataverse/entities/facade/DatasetBuilder.java
For context I'm using this client to interact with an implementation of the dataverse project. The issue is that there are some differencies between the basic dataverse native API and this implementation. There are some aditional optional or mandatory fields. For this reason I wanted to extend a few classes to add these. But this has proven to be quite difficult.
The text was updated successfully, but these errors were encountered: