Adding manual instruction to save file to system when automatic save fail #301
Conversation
This file contains 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
rchaurase
changed the title
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.
Starting-issue-485
This PR includes updates to the Getting Started Building an Application documentation. Specifically, I have added instructions for manually saving JSON output when the "Save to File System" button fails in the ODK-X Application Designer.
A new section for Manual Saving was added under the note explaining the automatic update process for definition.csv and properties.csv files.
This section includes detailed steps for manually copying and saving JSON files like formDef.json and other necessary files when automatic saving does not work.
What new issues will need to be opened because of this PR?
No new issues are expected to arise from this PR.
What is left to be done in the addressed issue?
There is nothing left to be done regarding this issue. The documentation now includes clear instructions for handling the JSON file-saving process.
What problems did you encounter?
No major issues were encountered during the update. The changes were straightforward, primarily focused on improving clarity in the documentation.