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
This makes total sense as compositions are composed left-to-right, however if you don't explicitly understand how your composition looked (or if you compose on someone else's object) bad things will happen.
This all makes sense and you'll end up with one well arranged composition. But what happens if the author of X decides to add a two method? Well, we're already shadowing it in XY, so the final composition will have two from XY. This is most likely what the application developer expected, but is it what the author of X expected?
This ticket tracks a proposal to add something like an unhandledShadowResolution callback to Factory that by default throws, but allows the developer to implement logic to choose what value to compose for a given property.
The text was updated successfully, but these errors were encountered:
We'd like to add custom shadow resolution when composing two specs with overlapping properties but different values.
Imagine this composition:
This makes total sense as compositions are composed left-to-right, however if you don't explicitly understand how your composition looked (or if you compose on someone else's object) bad things will happen.
Imagine the following composition:
This all makes sense and you'll end up with one well arranged composition. But what happens if the author of
X
decides to add atwo
method? Well, we're already shadowing it inXY
, so the final composition will havetwo
fromXY
. This is most likely what the application developer expected, but is it what the author ofX
expected?This ticket tracks a proposal to add something like an
unhandledShadowResolution
callback toFactory
that by default throws, but allows the developer to implement logic to choose what value to compose for a given property.The text was updated successfully, but these errors were encountered: