Currently the ProfileVersionBuilder is able to create a ProfileBuilder which the user can use to create profile and add them to the version, like the snippet below:
We could remove the need of carrying around the version builder instance by allowing the ProfileVersionBuilder to use a nested profile builder. The snippet above could become:
This is a small improvement in terms of cleaness, but does remove the burden of having to keep track which are the builder ones need to hold a reference to.
This PR adds the concept of composite/nested builder and applies it in the example above.
Currently the ProfileVersionBuilder is able to create a ProfileBuilder which the user can use to create profile and add them to the version, like the snippet below:
We could remove the need of carrying around the version builder instance by allowing the ProfileVersionBuilder to use a nested profile builder. The snippet above could become:
This is a small improvement in terms of cleaness, but does remove the burden of having to keep track which are the builder ones need to hold a reference to.
This PR adds the concept of composite/nested builder and applies it in the example above.