Improve clarity about file uploads (some can't discern that it went through)
Maintainers usually reply within 6 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- flask, javascript, python
Research direction
Start with the file-upload flow and the Dropzone widget's success section described in the issue, then review the original report for context. Choose one of the proposed feedback approaches and verify that a user can tell which course received the upload after submitting.
Written by the indexing model from the issue text.
Description
Original report by Scott Heggen (Bitbucket: sheggen, GitHub: sheggen).
Two ideas: 1) make a submit button that doesn't really do anything but reload the page, or 2) add a flash message indicating which course the file was successfully uploaded for (would go easily in the success section of the dropzone widget).
- Dominant language
- CSS
- Stars
- 0
- Forks
- 9
- Avg merge
- 9d 22h
- Merged PRs (30d)
- 4
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from BCStudentSoftwareDevTeam/bcsr
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
BCStudentSoftwareDevTeam/bcsr#135 ·
Maintainers usually reply within 6 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
BCStudentSoftwareDevTeam/bcsr#132 · 1 comment ·
Maintainers usually reply within 6 days
-
Prefix type enforcementPossibly taken @Ayeyomeday claimed this 2 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
BCStudentSoftwareDevTeam/bcsr#131 · 1 assignee ·
Maintainers usually reply within 6 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
BCStudentSoftwareDevTeam/bcsr#130 ·
Maintainers usually reply within 6 days
-
Add Github Pull Request TemplatePossibly taken @praveendse claimed this 16 days ago. Opengood first issue
Difficulty 1/5 Under an hour Newbie friendliness 88/100
BCStudentSoftwareDevTeam/bcsr#115 · 1 comment ·
Maintainers usually reply within 6 days
All issues in BCStudentSoftwareDevTeam/bcsr
Similar issues
-
fix(data-lake): wizard source step still previews the local slug, not the server-disambiguated oneOpendata-lake
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
enhancement good first issue priority: low size: XS
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
streamplace/streamplace#1351 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
chingu-voyages/V62-tier3-team-33#275 ·
Maintainers usually reply within 1 day