-
Notifications
You must be signed in to change notification settings - Fork 119
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
New arcgis-rest-features package w/ getFeature()
to get a feature b…
#115
Conversation
Oh, and @patrickarlt - I can't run the docs site, even on master, so this PR doesn't include any changes (if any) that are needed over there. It seems to hang on ➜ arcgis-rest-js git:(master) npm run docs:serve
> @esri/arcgis-rest-js@1.0.2 predocs:serve /Users/tom/code/arcgis-rest-js
> npm run docs:typedoc
> @esri/arcgis-rest-js@1.0.2 docs:typedoc /Users/tom/code/arcgis-rest-js
> node docs/build-typedoc.js
Using TypeScript 2.4.1 from /Users/tom/code/arcgis-rest-js/node_modules/typedoc/node_modules/typescript/lib |
because getFeature({
url: serviceUrl,
id: 42,
session?: IUserSession
} as IFeatureRequestOptions) see #78 |
@tomwayson What's the reasoning for naming the package Also, I think |
Good question @noahmulfinger. When I stared on this package, I thought a lot about the name. The first conclusion I came to was that I don't think we should avoid appending So, I was thinking that the best name for this package, and the best way to be consistent w/ Once I made the name about the service rather than the features, the only other peer out of the other pacakges (-auth, -common-types, -geocoder, -request) was really Also, back in #46 you and I both flip flopped back and forth btw/ |
@tomwayson Okay, thinking about it more, |
Thanks @noahmulfinger. I'm still torn, I like A way we could standardize on non-pulral names would have been: |
@tomwayson Yeah, I see what you mean. However, I don't think we will need to append And, at least in this case, I think the full term |
Good point. As per a discussion w/ @jgravois we're going to hold on merging this until he can cut a release w/ the fixes since 1.0.2 since this will require a minor bump. Also, FYI I've got |
getFeature()
to get a feature b…getFeature()
to get a feature b…
getFeature()
to get a feature b…getFeature()
to get a feature b…
…y id
begins to address #46
Started w/
getFeature()
just to wire up the new package and run the names by you as I shortened what I proposed in #46 (comment) fromgetFeatureById()
togetFeature()
b/c that seemed more in line w/getItem()
.