fix: object client methods can receive dict or list as default_value

[federicobond]

This PR

Updates client object methods to accept dict or list as default value.

[codecov]

Codecov Report

Merging #134 (805089a) into main (d31b531) will not change coverage.
The diff coverage is n/a.

@@ Coverage Diff @@## main #134 +/- ##
=======================================
Coverage 93.09% 93.09% =======================================
Files 20 20 Lines 362 362 =======================================
Hits 337 337 Misses 25 25 

Flag	Coverage Δ
unittests	93.09% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
open_feature/open_feature_client.py	96.47% <ø> (ø)

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[hlipsig]

LGTM I don't see anything wrong with it from a code perspective. This change is straighforward and easy to understand. I'm double checking there's not any obscure reason in our codebase that this shouldn't be done.

[Kavindu-Dodan]

@federicobond can we add few test cases to cover this scenario ? This will help to validate this change as well as not break this with future changes

[federicobond]

@Kavindu-Dodan sure! Not sure what kind of tests are you referring to, but I did update the one I found that was missing the list case.

[federicobond]

To get proper type testing we would have to run mypy or some other typechecker in some example code, but I think this exceeds the scope of this pull request.

[federicobond]

Replaced get_object_value for get_object_details in test case. Everything should be green now.

[Kavindu-Dodan]

@Kavindu-Dodan sure! Not sure what kind of tests are you referring to, but I did update the one I found that was missing the list case.

Sorry for not being specific. I was referring to the handling list type and seems you already added that.