Skip to content
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

Add new fields to WINS Display Review and _wins-data.json #5472

Open
1 of 16 tasks
Tracked by #5470 ...
roslynwythe opened this issue Sep 10, 2023 · 40 comments
Open
1 of 16 tasks
Tracked by #5470 ...

Add new fields to WINS Display Review and _wins-data.json #5472

roslynwythe opened this issue Sep 10, 2023 · 40 comments
Labels
Complexity: Large P-Feature: Wins Page https://www.hackforla.org/wins/ Ready for Prioritization role: back end/devOps Tasks for back-end developers size: 3pt Can be done in 13-18 hours
Milestone

Comments

@roslynwythe
Copy link
Member

roslynwythe commented Sep 10, 2023

Dependency

Overview

We need to create new fields to hold only GitHub and LinkedIn handles (in contrast to the current fields which contain complete URLs), and to incorporate those fields into the Response sheet, Review sheet, and the _wins-data.json feed.

Details

We set up validation on the wins form so that users could give us the handles, with and without URL prefixes, now we need to take only the handle into the relevant sheets, so that we can (in another issue) update the .js files.

Ultimately, the goal is to have the URLs on the wins page (you can see them when you hover over the LinkedIn and GitHub icons), have a standard format. See epic for more details.

Action Items

  • This issue will require modification of the code the Apps Script wins-form-responses within the Wins-form (responses)1 sheet, but you will require a Google Drive test environment that includes copies of Wins-form (Responses)1, gh-requests2, and Wins-form[^6]. It will also be useful to read Wins Form Admin Guide3. It will also be necessary to setup a test environment in your GitHub repository. Follow instructions in the comment in the Hfla Google Apps Script Development Process Guide4 and Testing WINS in a test repository5
  • As described in section 3a and 3b of the Hfla Google Apps Script Development Process Guide4, 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 Guide3 as VIEWER
    • share the Wins-form (Responses)1 sheet as VIEWER
    • share the gh-requests doc as VIEWER
    • make a copy of Wins-form, including the issue # in the name, then share that copy with the developer as EDITOR.
  • Continue following instructions in 3c and d. As described in 3d, you will have to make modifications to certain documents in the test folder.
    • In the test folder, you must edit the Responses settings of the Wins-form so that test submissions will be stored in the Wins-form (Responses} that is in the test environment
    • Setup triggers so that insertLatestFormSubmitIntoReviewSheet and createIssue functions will execute when a form is submitted
    • 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.
  • In the Response sheet, create two new columns GitHub-handle and LinkedIn-name
  • In insertLatestFormSubmitIntoReviewSheet populate the new columns with strings extracted from the submitted data in the GitHub URL and LinkedIn URL columns in the Response sheet.
  • Display the values of GitHub-handle and LinkedIn-name, along with the submitted data for GitHub URL and LinkedIn URL, on the Review sheet.
  • In main add code to include the GitHub-handle and LinkedIn-name fields in _wins-data.json
  • Refer to Section 7 "Testing" in the Hfla Google Apps Script Development Process Guide4 , Test the code by running main() in debug mode. A new pull request "Update wins-data.json via Google Apps Script" should be appear in your test repository. Examine the json data and if it looks good, merge into your repository test branch, bring that branch down to your local workstation and and use Docker to examine the resulting Wins page, which should remain unchanged.
  • Refer to Section 8 "Completing an Issue" in the Hfla Google Apps Script Development Process Guide4 , for information about commiting Code.js and creating a pull request.
  • In the pull request, provide links to the "Update wins-data.json via Google Apps Script" Pull Request and also the Wins page (both in your repository), for the convenience of reviewers.
  • Contact a dev lead to discuss review/demonstration

Resources/Instructions

Footnotes

  1. Wins-form (Response) Sheet 2 3

  2. gh-requests

  3. Wins Form Admin Guide 2

  4. Hfla Google Apps Script Development Process Guide - draft 2 3 4

  5. Testing WINS in a test repository

@roslynwythe roslynwythe added Feature Missing This label means that the issue needs to be linked to a precise feature label. role missing size: missing labels Sep 10, 2023
@github-actions

This comment has been minimized.

@roslynwythe roslynwythe added Complexity: Large P-Feature: Wins Page https://www.hackforla.org/wins/ role: back end/devOps Tasks for back-end developers size: 2pt Can be done in 7-12 hours Draft Issue is still in the process of being created and removed Feature Missing This label means that the issue needs to be linked to a precise feature label. role missing size: missing labels Sep 10, 2023
@anjolaaoluwa anjolaaoluwa added this to the 03.02 Onboarding flow milestone Sep 10, 2023
@kimberlytanyh kimberlytanyh added the Dependency An issue is blocking the completion or starting of another issue label Sep 10, 2023
@ExperimentsInHonesty ExperimentsInHonesty added ready for dev lead Issues that tech leads or merge team members need to follow up on and removed Dependency An issue is blocking the completion or starting of another issue labels Jan 24, 2024
@ExperimentsInHonesty

This comment was marked as duplicate.

@roslynwythe roslynwythe added Ready for Prioritization and removed Draft Issue is still in the process of being created ready for dev lead Issues that tech leads or merge team members need to follow up on labels Jan 26, 2024
@roslynwythe roslynwythe self-assigned this Jan 29, 2024
@roslynwythe roslynwythe added the Draft Issue is still in the process of being created label Jan 29, 2024

This comment has been minimized.

@roslynwythe roslynwythe added Ready for Prioritization and removed ready for dev lead Issues that tech leads or merge team members need to follow up on labels Oct 15, 2024
@ExperimentsInHonesty ExperimentsInHonesty added ready for dev lead Issues that tech leads or merge team members need to follow up on Draft Issue is still in the process of being created and removed Ready for Prioritization labels Oct 15, 2024
@HackforLABot

This comment was marked as outdated.

@roslynwythe roslynwythe added Ready for Prioritization and removed Draft Issue is still in the process of being created ready for dev lead Issues that tech leads or merge team members need to follow up on labels Nov 3, 2024
@roslynwythe roslynwythe removed their assignment Nov 3, 2024
@ExperimentsInHonesty ExperimentsInHonesty added Draft Issue is still in the process of being created and removed Ready for Prioritization labels Nov 5, 2024
@HackforLABot

This comment was marked as outdated.

@roslynwythe roslynwythe added Ready for Prioritization and removed Draft Issue is still in the process of being created labels Nov 8, 2024
@ExperimentsInHonesty

This comment was marked as outdated.

@ExperimentsInHonesty ExperimentsInHonesty added ready for dev lead Issues that tech leads or merge team members need to follow up on Draft Issue is still in the process of being created Added to dev/pm agenda and removed Ready for Prioritization labels Nov 12, 2024
@roslynwythe roslynwythe removed ready for dev lead Issues that tech leads or merge team members need to follow up on Added to dev/pm agenda Draft Issue is still in the process of being created labels Nov 19, 2024
@roslynwythe roslynwythe removed their assignment Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Large P-Feature: Wins Page https://www.hackforla.org/wins/ Ready for Prioritization role: back end/devOps Tasks for back-end developers size: 3pt Can be done in 13-18 hours
Projects
Status: New Issue Approval
Development

No branches or pull requests

8 participants