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
and then, in the resolver implementation, we first fetch the intloc by <intloc> and then fetch the location1.
We could optimize this given that now we "control" the $ref when we create/update records by also adding the location pid.
ensure that on create/update we completely ignore any user input for the location field and instaed we re-create the $ref from the field location: ABC, e.g. $ref: ".../resolver/internal_location/<intloc>/location/ABC"
change the refs URLs and add the referenced record pid, whenever possible and makes sense.
Having both current record and referenced record in the resolver implementation function is far more flexible.
The text was updated successfully, but these errors were encountered:
Currently we have implemented resolvers URLs that contain the current record pid, e.g.
and then, in the resolver implementation, we first fetch the intloc by
<intloc>
and then fetch thelocation
1
.We could optimize this given that now we "control" the
$ref
when we create/update records by also adding the location pid.location
field and instaed we re-create the$ref
from the fieldlocation: ABC
, e.g.$ref: ".../resolver/internal_location/<intloc>/location/ABC"
Having both current record and referenced record in the resolver implementation function is far more flexible.
The text was updated successfully, but these errors were encountered: