fixing response view in frontend JS #48
Open
Conversation
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
- added the response.json() according to the change in index.html - removed the part about the project trigger entirely, because, as a reserved function, doPost(e) is part of the simple triggers in GAS and should work without adding a custom trigger
messed up this link by removing a section
also messed up this links
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.
Response {type: "cors", url: "...", redirected: true, status: 200, ok: true, …}, no matter what i returned from the doPost method in GASresponse.json()into the Promise chaindoPost(e)is already a reserved function and as such part of the Simple triggers. thus i removed the installed trigger for me and everything still worked. so i removed this section from README.md. in this PR