Conversation
cli call looks OK but the app isn't loading data
Needed to set the file name to track
bb7738a to
b6c0684
Compare
Collaborator
Author
|
I'll need to rebase this on |
Contributor
should I wait on the review till this is done? |
Collaborator
Author
|
@doc-han yes please - unless you wanted to take over the PR 😇 I doubt I'll get to it this week |
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
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
This PR ports the legacy metadata service into the new collaborative editor
(no issue but it came out of #4386 )
Background
Metadata in this context refers to database/entity metadata pulled from the target backend service. So if you're editing a Salesforce step, the metadata is all the sObjects in the Salesforce instance the credential points to. If you're editing DHIS2, it's all the entities and attributes and stuff defined in the DHIS2 instance your credential points to.
Metadata was a bit of an experiment we did back in the day that never quite took off. We only support metadata for dhis2 and salesforce.
Metadata shows up in two places:
Validation steps
https://play.im.dhis2.org/stable-2-42-3-1useradminand passworddistrictcreate()(you should get code assist but maybe try ctrl + space)tracked-entity)AI Usage
Please disclose whether you've used AI anywhere in this PR (it's cool, we just
want to know!):
You can read more details in our
Responsible AI Policy