Possible Improvement in Field Validation #962
Replies: 2 comments 1 reply
-
Your code have some bugs. For example. self._parent can be None. In this case it will produce an error. I didn't write this portion of the library code, but pycharm tells me that @jtweeder did it a long time ago. Maybe he can help here? Thanks |
Beta Was this translation helpful? Give feedback.
-
I should have some time in the coming days to refresh my memory and provide some input. I believe the intent of that segment was to check known field names against what sharepoint was expecting based on the known field names. Giving it an opportunity to fail before wasting an API call for sending the wrong column name. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, thanks in advance for this lib it helps me a lot with my activities. but I think there is a problem in method responsible to check field validation before update it:
As the validation of parent fields is done after an "else" statement it will only check for this if there are no child fields, but this is a problem because if you have a null field on child, it yet can be a valid in your parent. I made this change on a fork and it works well for me:
So I don't know if you have some special assumption about this and this is why I didn't make a pull, but I think it's good warn
Beta Was this translation helpful? Give feedback.
All reactions