API docs for custom actor properties on app users and links#1831
Open
ktuite wants to merge 2 commits into
Open
API docs for custom actor properties on app users and links#1831ktuite wants to merge 2 commits into
ktuite wants to merge 2 commits into
Conversation
ktuite
force-pushed
the
ktuite/audit_log_actor_properties
branch
from
32f344a to
e9b7fe2
Compare
ktuite
force-pushed
the
ktuite/api_docs_actor_properties
branch
from
d821872 to
eb81c52
Compare
ktuite
force-pushed
the
ktuite/api_docs_actor_properties
branch
from
eb81c52 to
81e8069
Compare
ktuite
force-pushed
the
ktuite/api_docs_actor_properties
branch
from
81e8069 to
aea6fd7
Compare
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
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.
API Docs part of getodk/central#1868:
What has been done to verify that this works as intended?
Why is this the best possible solution? Were any other approaches considered?
How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?
Does this change require updates to the API documentation? If so, please update docs/api.yaml as part of this PR.
Before submitting this PR, please make sure you have:
make testand confirmed all checks still pass, or witnessed Github completing all checks with success