This change got buried in a stashed commit during my last PR, but since set_attributes now processes the id field, it would ideally disallow NA values from being set on it.
With that said, it might make sense for set_attributes to set the id with whatever value it was passed (NA or otherwise) and maybe should not be the responsibility of this function to coerce an NA to NULL for this field,- but my opinion is that it is appropriate and useful to integrate that in here, since an NA value for id would never be desirable or valid.
This change got buried in a stashed commit during my last PR, but since set_attributes now processes the id field, it would ideally disallow NA values from being set on it.
With that said, it might make sense for set_attributes to set the id with whatever value it was passed (NA or otherwise) and maybe should not be the responsibility of this function to coerce an NA to NULL for this field,- but my opinion is that it is appropriate and useful to integrate that in here, since an NA value for id would never be desirable or valid.