-
-
Notifications
You must be signed in to change notification settings - Fork 766
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Google Apps Script: Fix extra empty JSON field problem #3417
Comments
This comment was marked as outdated.
This comment was marked as outdated.
Hi @aricforrest, thank you for taking up this issue! Hfla appreciates you :) Do let fellow developers know about your:- You're awesome! P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :) |
Availability: Monday-Wednesday 5 PM - 7 PM PST |
Blocker - Unable to replicate the bug of empty key value pairs in JSON in my own Google Apps Scripts instance using a copy of @luke-karis created this issue on July 21, 2022 and completed updating another Wins process issue #2901 on September 17, 2022 so I'm wondering if this bug has already been resolved. Data in any columns after O in the spreadsheet would cause similar behavior as described by this bug. However, the bot's most recent PR (#3024) to update the Wins JSON files still show the empty key-value pairs. Google Apps Scripts aren't being stored in GitHub to check to see what changes were made for issue #2901 so I've created issue #3641 to begin storing/tracking Google Apps Scripts also in GitHub. Should I copy the current
|
Google's Advanced Protection enabled on an account prevents running Apps Scripts from unverified/unapproved apps. A work around is to add the following block at the top of the script, but due to the
I am creating a new Google account without Advanced Protection enabled and sharing the Google Share with it to continue working on this issue. |
The API token for the |
|
Issue is ready for review @hackforla/website-merge |
@hackforla/website-merge I am not sure if this is fixed or it was determined that its not a problem or it couldn't be determined that its not a problem because of the token issue #3748 |
Closing issue since issue seems to have been fixed. |
Overview
In the _wins-data.json and wins-data.json at the end of each Wins entry, there is "":"", which wasn't there in the current _wins-data.json and current wins-data.json in gh-pages. The objective of this ticket is to figure out why this is happening and implement a fix.
Action Items
Resources/Instructions
The PR where the updated wins data goes to is here #3024. You can see the issue described by this ticket by going to the files changed tab in this PR and scrolling through one of the wins-data files until you reach the end of an entry.
The text was updated successfully, but these errors were encountered: