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
Cliff Click commented: Minor tweak to the API - general philosophy is to choose positive over negatives. So yes, included is better than excluded, even if the included-list is likely to be large all the time.
Raymond Peck commented: I talked with Patrick about this the other day, and my proposal was to allow the client to specify either the included or the excluded (error out if they specify both), and always convert that in the REST API layer to the current ignored_columns mechanism.
Should ignored_columns on all the model builders be changed to included_columns?
cc [~accountid:557058:abbecef9-9266-49cd-a13f-d0c5d27cb5da], [~accountid:557058:1529d34e-fbf0-45b1-8f33-facc04ecb672]
The text was updated successfully, but these errors were encountered: