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
Atm they get a number of props, including the extraContext, but that is the whole row, which is not that useful in case ref-scheme is used to point to a nested property. We need a new injected property (eg entry) that will hold the immediate parent of the value.
This way the widget will have an easy way to use other properties of the object whose value it renders.
See:
I think we should just need to call _.toPath with the refScheme, then run a _.get w/o the last entry to get the parent object, and finally an extra _.get with the last part of the path to get the value.
Atm they get a number of props, including the
extraContext
, but that is the whole row, which is not that useful in case ref-scheme is used to point to a nested property. We need a new injected property (egentry
) that will hold the immediate parent of the value.This way the widget will have an easy way to use other properties of the object whose value it renders.
See:
rendition/src/extra/AutoUI/index.tsx
Lines 510 to 516 in f10cecc
The text was updated successfully, but these errors were encountered: