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

Login Errors + Event Field Terminology #85

Closed
ThatMegamind opened this issue Apr 18, 2024 · 0 comments · Fixed by #89
Closed

Login Errors + Event Field Terminology #85

ThatMegamind opened this issue Apr 18, 2024 · 0 comments · Fixed by #89
Assignees
Labels

Comments

@ThatMegamind
Copy link
Collaborator

Part 1: Login Errors Match Hi-Fi

  • Currently, several errors that appear when attempting to Login simply appear as "Firebase: Error (auth/invalid-credential)."
  • However, the error messages that appear should be more descriptive and relate more to the specific error occurring
  • This task is to match each error shown in the high-fidelity design with the appropriate error message (ex. "Account could not be found with given information. Please check your username or password and try again." for entering incorrect information)
  • Contact Diana if you need any clarification on the exact scenarios that cause each error!
  • Login High Fidelity Design

Part 2: Make Event Field Terminology Consistent

  • In the AISS system, two fields for Catalog events are inconsistently worded: subject and event type
  • The correct terminology is currently found in the form for creating an event in the Catalog, shown here:
Screenshot 2024-04-17 at 9 19 36 PM
  • However, in other parts of the system, the wording is slightly different. The task is to fix every occurrence of these fields to use the correct terminology, including:
    • The dropdown filters on the Catalog (currently says "Topic" and "Type")
Screenshot 2024-04-17 at 9 24 29 PM
  • The form used to add events to the Published Schedule (currently uses "Topic")
Screenshot 2024-04-17 at 9 24 00 PM
  • Any others that you find!
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants