No preview data generated when @Dowel data class has default values

[savvasdalkitsis]

Library Version: 0..8.0

Describe the Bug:
assuming a class:

data class Test(
    val name: String = "",
    val age: Int? = null,
)

The generated provider class only contains empty constructor invocations, generating the same data for each entry.

If you remove the default values, the correct provider class is generated

[jayasuryat]

Yes, right now @Dowel ignores all the properties with default values for code-generation.

I can see how this might be inconvenient in certain use-cases.

---

I think code generation could be added for properties with default values, given, their types are supported by Dowel. Otherwise, could back-off to rely on the existing behaviour.

I don't have any immediate concerns with the above mentioned approach, will think through different cases, and if everything checks out, will add support for this in the next release.

[mohsen-biglari]

A suggestion for including this functionality could be a new param for @Dowel to be able to toggle this behavior. Something like:

@Dowel(ignoreDefaultValues: Boolean, ...)

[jayasuryat]

Yep, @mohsen-biglari, that should work.

---

I'm also thinking if having this configuration at a property level would be needed or not.

For example,

@Dowel(count = 30, ignoreDefaultValues = true)
data class Person(
    val id: Long = 1L,
    val name: String,
    val bio: String?,
    @DrawableRes val avatar: Int = R.drawable.ic_launcher_foreground,
)

In this example, I may want to generate random values for the id property, but would want to keep the avatar as is with the default value.

@savvasdalkitsis what do you think?

[savvasdalkitsis]

I would probably name the property something like preserveDefaultValues or doNotOverrideDefaultValues to make it clear what will happen but looks good otherwise

[jayasuryat]

@savvasdalkitsis, my question is, do you see it as necessary to configure this at the property level, or is class-declaration level configuration sufficient?

[jayasuryat]

@savvasdalkitsis, this has been implemented and would be part of the next release.

---

For now, this solution only addresses this configurability at a class level.

I'm still evaluating the need for this configurability at a property level, which if needed would be an additive change, anyway.

[jayasuryat]

@savvasdalkitsis this has been released as part of the v0.9.0 release. Check it out whenever you get a chance next!