Closed mtrezza closed 1 year ago
@dblythy What do you think?
Sounds good
To avoid any confusion for future readers, in your PR you're passing the name of the selected field, instead of the value of the selected field as suggested in the example use case. I think that makes more sense, because if there are 2 fields of the same type with the same value it wouldn't be possible to know which field was selected.
🎉 This change has been released in version 5.2.0-alpha.23
🎉 This change has been released in version 5.3.0-beta.1
🎉 This change has been released in version 5.3.0-alpha.1
🎉 This change has been released in version 5.3.0
New Feature / Enhancement Checklist
Current Limitation
Currently, it cannot be determined which field was been selected when a script has been invoked.
Feature / Enhancement Description
Pass the selected field as a separate parameter to the Cloud Function payload.
For example the dashboard user should be able to invoke a script on a user in a specific field of the selected object:
Knowing only the "transaction" object is not enough to know on which user the Cloud Function should be executed.
Example Use Case
Alternatives / Workarounds
None.