map-extent documentation #136
Merged
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.
documenting changes in relation to Maps4HTML/MapML.js#887 and adding to the already merged PR #135
Add documentation for hidden attribute for layer to reflect this code for query layers on MapMLLayer.js -> getQueryTemplate: - document that the query does not work if layer is hidden - to be documented after map-link dev.hidden
layer containing a query throws exception MapML.js#904For our API's we learned that they can only be used after the custom element is attached to the DOM. This needs to be reflected on the web-map-doc. Found using the features API experiment.no longer an issuemap-change
event forlayer-
element.Document the use of map-meta's inside of map-extents and how they work:- Should be added after it is finalized in the map-link PR work