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
I just opened this PR for adding support for reading status property configs, which was core to my use case.
Even if it's accepted, I'm still unclear on the best way to add support for parsing the status property type into a StatusPropertyConfig while also preventing the StatusPropertyConfig from being used as an input for the DatabaseClient.Create() and DatabaseClient.Update() methods.
Perhaps we could add a methods to DataBaseUpdateRequest and DatabaseCreateRequest that would remove any incompatible PropertyConfigs assigned to them?
I've not investigated this thoroughly, but it doesn't appear to me that the .Update() method has any logic in place to prevent other invalid PropertyConfigs, e.g. formula from being passed in as values.
Would love to hear your thoughts!
The text was updated successfully, but these errors were encountered:
I just opened this PR for adding support for reading status property configs, which was core to my use case.
Even if it's accepted, I'm still unclear on the best way to add support for parsing the status property type into a StatusPropertyConfig while also preventing the StatusPropertyConfig from being used as an input for the DatabaseClient.Create() and DatabaseClient.Update() methods.
Perhaps we could add a methods to
DataBaseUpdateRequest
andDatabaseCreateRequest
that would remove any incompatible PropertyConfigs assigned to them?I've not investigated this thoroughly, but it doesn't appear to me that the
.Update()
method has any logic in place to prevent other invalid PropertyConfigs, e.g.formula
from being passed in as values.Would love to hear your thoughts!
The text was updated successfully, but these errors were encountered: