This repository was archived by the owner on Mar 31, 2020. It is now read-only.
Keep featureservicetools from returning ags object#350
Open
kevinmmsd wants to merge 2 commits intoEsri:masterfrom
Open
Keep featureservicetools from returning ags object#350kevinmmsd wants to merge 2 commits intoEsri:masterfrom
kevinmmsd wants to merge 2 commits intoEsri:masterfrom
Conversation
Change method of determining agol vs ags in featureservicetools
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Modify featureservicetools.py to use the is_portal member of the security handler instead of the absence of layers in the feature service to decide to return an ags.FeatureService. I'm a little less confident of this as I'm not using portal at all. Was having problems with getting the ags object when working with empty agol feature services.