4 ms·
Someones hasn't tested or checked their code before deployment. Because there is an error on the page: "TypeError: ReactOnRails encountered an error while r
by rvz 3y ago
Someones hasn't tested or checked their code before deployment. Because there is an error on the page:
"TypeError: ReactOnRails encountered an error while rendering component: ArticlesShowPage"
Original message: Cannot read properties of null (reading 'children')
at F (ArticlePage.tsx:532:27)
Ironically the point of TypeScript is to check for type errors before transpiling to JavaScript and before deployment. Yet we still see this 'TypeError' issue once again.
- foolswisdom 3y ago(for anyone who was confused like me, we know they're using typescript from the `.tsx` extension in the traceback)
- dpistole 3y agoWonder if it's tsconfig 'strictNullChecks', I think by default it's false, takes a lot away from the typesafety I worked on a codebase missing it once and when I went to turn it on there were thousands of errors to fix so we left it off