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

feat: Add Schedule Unique Identifier to Screenshot File Name #470

Open
FlyteWizard opened this issue May 1, 2023 · 1 comment
Open

feat: Add Schedule Unique Identifier to Screenshot File Name #470

FlyteWizard opened this issue May 1, 2023 · 1 comment
Labels
enhancement New feature or request frontend Frontend (UI) related issues good first issue Good for newcomers

Comments

@FlyteWizard
Copy link
Member

As a student I want to be able to take screenshots of multiple schedules without having to manually modify the file name for each different schedule.

Reasoning:

  • I have schedule A and schedule B.
  • I screenshot schedule A as 202305_calendar.png (i.e., default file name).
  • I then screenshot schedule B, but I need to manually edit the file name to 202305_calendar_b.png (the default file name is increment to 202305_calendar-2.png by default on OS).

Proposal: Add the schedule unique identifier (i.e., httos://courseup.vikelabs.ca/s/nsmChzvmCYaD) to the file name. OR Add the courses of the schedule to the file name.

Example: 202305_calendar_nsmChzvmCYaD.png OR 202305_calendar_csc423a02_csc260a02_math202a01_math202t03.png.

Notes: The feature can be classified as a Good First Issue.

@szeckirjr szeckirjr added enhancement New feature or request good first issue Good for newcomers frontend Frontend (UI) related issues labels Jul 6, 2023
@szeckirjr
Copy link
Contributor

It would be cool to have a default value with an option to save the name before downloading too
quick figma sketch:
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request frontend Frontend (UI) related issues good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants