-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make moveItem's folder parameter optional #306
Conversation
@@ -27,7 +27,7 @@ export interface IItemMoveRequestOptions extends IItemCrudRequestOptions { | |||
* Alphanumeric id of folder to house moved item. If null, empty, or "/", the destination is the | |||
* root folder. | |||
*/ | |||
folder: string; | |||
folder?: string; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
my preference would be to use folderId
consistently instead of folder
.
see #236
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jgravois, I agree, but then it would be different than the corresponding parameter in the REST call (https://developers.arcgis.com/rest/users-groups-and-items/move-item.htm); is that OK?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes. I think the REST parameter name is a footgun.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, we're even less clear about our guidelines (or lack thereof) on trying to stick to the shape (names, etc) of the REST API, except in those cases where it doesn't make sense. Some ambiguous balance of replicating an API that people are already familiar with and building the API we would want to use.
No description provided.