You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the console, we fixed an issue with orga names starting with spaces.
When orga names started with spaces, it triggered weird displays in the console menu and it triggered an error in the cc-header-orga component
Uncaught(inpromise) TypeError: Cannotreadpropertiesofundefined(reading'toUpperCase')atcc-header-orga.js:60:90atArray.map(<anonymous>)
at Object.render (cc-header-orga.js:60:76)
at Object.update (lit-element.ts:160:24)
at Object.performUpdate (reactive-element.ts:1331:14)
at Object.scheduleUpdate (reactive-element.ts:1263:17)
at Object.__enqueueUpdate (reactive-element.ts:1235:25)
We fixed this in the console by using trim on orga names when they are edited and doing the same in db for existing orgas.
Still, it would be best if the component could handle this issue, just in case.
Solution
Trim the orga name when getting the initials.
The text was updated successfully, but these errors were encountered:
Context
In the console, we fixed an issue with orga names starting with spaces.
When orga names started with spaces, it triggered weird displays in the console menu and it triggered an error in the
cc-header-orga
componentWe fixed this in the console by using
trim
on orga names when they are edited and doing the same in db for existing orgas.Still, it would be best if the component could handle this issue, just in case.
Solution
Trim the orga name when getting the initials.
The text was updated successfully, but these errors were encountered: