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
Is your feature request related to a real problem or use-case?
An existing (possibly third party) type has nested readonly elements, but it would be handy to re-use that type and build up the final object which can only be done if the nested fields are updateable (i.e. not read only)
Is your feature request related to a real problem or use-case?
An existing (possibly third party) type has nested readonly elements, but it would be handy to re-use that type and build up the final object which can only be done if the nested fields are updateable (i.e. not read only)
e.g.
It would be nice to be able to do something like
Describe a solution including usage in code example
Should work just like the other Deep* types, but making nested elements mutable like Mutable already does.
Who does this impact? Who is this for?
All users who might be working with nested readonly types outside of their control (i.e. third party code)
Describe alternatives you've considered (optional)
Manually recreate the original type as non-readonly, but that's certainly not ideal.
Additional context (optional)
Could potentially use the features described in #151 and serve as a template/example for that refactoring.
Also, just want to say thanks for making and maintaining this library!
The text was updated successfully, but these errors were encountered: