feat: move 3dtiles service to maps collection #2010
+4
−3
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.
Description: Moves 3dtiles service type to maps collection from other collection
Instructions for testing:
Closes Issues: # (if appropriate)
Updated meaningful TSDoc to methods including Parameters and Returns, see Documentation Guide
used semantic commit messages
PR title follows semantic commit format (CRITICAL if the title is not in a semantic format, the release automation will not run!)
Updated
peerDependencies
as needed. CRITICAL our automated release system can not be counted on to updatepeerDependencies
so we must do it manually in our PRs when needed. See the updating peerDependencies section of the release instructions for more details.These changes have been verified by QA using a
?uiVersion
that includes a PR-Preview of this branch and thev_req
label has been applied to the issue.OD-UI E2E tests pass against these changes using a
?uiVersion
that includes a PR-Preview of this branch*CRITICAL
If you are making a breaking change, make sure to add the
BREAKING CHANGE
comment in the merge commit message. If this is not done,semantic-release
will not do the right thing.If you find yourself in this position...
BREAKING CHANGE
message in the merge commit.npm deprecate @esri/{package-name}@v{version-you-don't-want-out}