chore: documents support for geoshape and geotrace in Web Forms#2020
Open
latin-panda wants to merge 6 commits intomasterfrom
Open
chore: documents support for geoshape and geotrace in Web Forms#2020latin-panda wants to merge 6 commits intomasterfrom
latin-panda wants to merge 6 commits intomasterfrom
Conversation
Contributor
Author
|
This is a draft tagged for |
latin-panda
changed the base branch from
master
to
web-froms-docs-geo-question-types
latin-panda
force-pushed
the
web-froms-docs-geoshape-geotrace-types
branch
from
0712d61 to
08f6e12
Compare
Contributor
Author
|
@alyblenkin What do you think of this doc? |
|
Yes, it's on my list to update today! |
latin-panda
commented
Feb 27, 2026
latin-panda
commented
Feb 27, 2026
Contributor
Author
|
@lognaturel this is ready for review :) |
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What is included in this PR?
What new issues will need to be opened because of this PR?
What is left to be done in the addressed issue?
What problems did you encounter?