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
When developing a feature I noticed the amount of warnings and errors that are being spammed throughout the console. While the pipeline still builds and the website still works, maintaining this project is becoming more and more time consuming.
❌The bad
We are using out of date technology - while we are using Gatsby 5, due to other package dependencies we aren't getting the full power from it
Using JS 😭
Locked package versions - We are using a lot of no longer maintained packages
Hard coded values - while we have some integration with CRM we still use hard coded values.
Terminal output is littered with errors, warnings and deprecation notices
Local build doesn't work - Causes fatal error
✅The good
People still runs
Pipeline still works
Using Prop-Types to give js some hope of type safety
Core foundations to improve upon
The Future
Option 1. Re-write this project
Start from scratch using the best practices from day 1 and build up the project with the aim to fully integrate People with CRM. With the aim of alleviating the need to update information in 2 places. A person updates information in CRM -> their Peoples page gets updated at the same time!
Option 2. Fix the issues
Slowly refactor the project, replacing JS with TS and removing and replacing Gatsby plugins with new solutions or build them if they don't exist while continuing to add new features.
The text was updated successfully, but these errors were encountered:
cc @bradystroud
Hi Team,
Description
When developing a feature I noticed the amount of warnings and errors that are being spammed throughout the console. While the pipeline still builds and the website still works, maintaining this project is becoming more and more time consuming.
❌The bad
✅The good
The Future
Option 1. Re-write this project
Start from scratch using the best practices from day 1 and build up the project with the aim to fully integrate People with CRM. With the aim of alleviating the need to update information in 2 places. A person updates information in CRM -> their Peoples page gets updated at the same time!
Option 2. Fix the issues
Slowly refactor the project, replacing JS with TS and removing and replacing Gatsby plugins with new solutions or build them if they don't exist while continuing to add new features.
The text was updated successfully, but these errors were encountered: