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

[My Projects] BUG: Unexpected Application Error! Cannot read properties of undefined (reading 'toLowerCase') #1552

Closed
ZekeAranyLucas opened this issue Dec 3, 2023 · 1 comment
Assignees
Labels
bug Release Note: Shows as Error Correction level: medium priority: MUST HAVE role: front-end Front End Developer size: missing

Comments

@ZekeAranyLucas
Copy link
Member

Overview

In My Projects, clicking on the header for the context menu (kebab menu) column has no effect but causes an error in the browser console.

REPRO

  1. login
  2. navigate to "My Projects" : http://localhost:3000/projects
  3. on the far right is a column header without text (rows contain a kebab button)
  4. click on the blank header above the kebabs.

EXPECTED

Nothing. it should not indicate the header is even clickable since it doesn't make sense.

RESULTS

Unexpected Application Error!
Cannot read properties of undefined (reading 'toLowerCase')
TypeError: Cannot read properties of undefined (reading 'toLowerCase')
    at descCompareBy (http://localhost:3000/static/js/bundle.js:25989:29)
    at http://localhost:3000/static/js/bundle.js:26001:83
    at http://localhost:3000/static/js/bundle.js:26006:21
    at Array.sort (<anonymous>)
    at stableSort (http://localhost:3000/static/js/bundle.js:26005:20)
    at ProjectsPage (http://localhost:3000/static/js/bundle.js:26080:26)
    at renderWithHooks (http://localhost:3000/static/js/bundle.js:112927:22)
    at updateFunctionComponent (http://localhost:3000/static/js/bundle.js:115809:24)
    at beginWork (http://localhost:3000/static/js/bundle.js:117521:20)
    at beginWork$1 (http://localhost:3000/static/js/bundle.js:122472:18)
💿 Hey developer 👋

You can provide a way better UX than this when your app throws errors by providing your own ErrorBoundary or errorElement prop on your route.

Debugger Console shows something similar and a few followups

@Biuwa
Copy link
Member

Biuwa commented Jan 17, 2024

Please provide an update:

  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 (if necessary)(Add any pictures that will help illustrate what you are working on):

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Release Note: Shows as Error Correction level: medium priority: MUST HAVE role: front-end Front End Developer size: missing
Projects
Status: On Dev - not yet pushed to Prod
Development

No branches or pull requests

4 participants