Google Apps Script: Add unique IDs as object keys for each wins entry

[macho-catt]

Dependency

• CLASP for Google Apps Scripts development evaluation / decision  #3722
• Add latest version of Google Apps Scripts to GitHub #3641
• Create wiki page "Hfla Google Apps Script Development/Review Process" #4134
• Google Apps Script: Migrate Wins Data - Stop generation of AF file #2147

Overview

To expedite the process of locating a specific wins entry, each wins entry (which is also a javascript object) should have a unique ID as a key.

Action Items

• Follow sections 1-3 in the Wins Apps Script Development Process¹. Note that in this issue you will be modifying both Apps Scripts wins-form-responses and gh-requests so setup will be required in both /google-apps-script/wins-form-responses and /google-apps-script/gh-requests
• As described in section 3a and 3b, you will provide a dev lead with the google account you wish to use for testing, and request the dev lead to:
  • do not modify folder level access
  • share the Wins Form Admin Guide² as VIEWER
  • share the Wins-form (Response)³ sheet as VIEWER
  • share the gh-requests doc as VIEWER
• Continue following instructions in 3c and d. As described in 3d, you will have to make modifications to certain documents in the test folder.
  • It will not be necessary to restore any triggers, because you can execute main() in debug mode.
  • Since you will be running main() for testing, you must follow instructions in Testing WINS in a test repository
• Continue following instructions through section 6 "Editing". As described in this section, editing can be done locally in an IDE or in the Google Drive cloud editor, and the clasp utility can be used to transfer code back and forth between the local worksation and the Google Drive as needed.
  • Modify wins so that on the creation of the javascript object for each entry, a unique ID is generated as well
  • This ID can be the row number of the wins entry
• Ensure that even with the addition of the unique IDs as keys, the current wins page should functionally look and work the same way in your own repo.
• Demo your changes to the website leads so they can approve and add it to the production script

Resources/Instructions

Google Apps Script
_wins-data file
wins page JS

Footnotes

1. Wins Apps Script Development Process ↩

2. Wins Form Admin Guide ↩

3. Wins-form (Response) Sheet ↩

[github-actions]

Hi @macho-catt.

Good job adding the required labels to this issue.

Additional Resources:
Wiki: How to add status labels to issues (WIP. Link will be updated when the wiki is done)
Wiki: How to create issues (WIP. Link will be updated when the wiki is done)

[lopezpedres]

Availability for this week: 10 hrs.
My estimated ETA for completing this issue: 2021/12/28

[github-actions]

@lopezpedres

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures: "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

_{You are receiving this comment because your last comment was before Monday, December 20, 2021 at 11:19 PM PST.}