Technical Debt Reduction: Fix Code Formatting and Lint Errors - #71
Merged
Conversation
…stant declarations for consistency
Collaborator
|
Ahhh...so clean. Confirmed works for me: was able to open existing project, modify it, edit template, create project. |
Collaborator
|
@jdanish Please give this PR a quick whirl on existing projects to make sure the code updates work. Sri power-washed our code. If it works, please merge. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
One major problem has been code format consistency due to Prettier being disabled in NetCreate 1.0 due to issues with the configuration files. This was corrected a couple months ago, so now it is time to clean everything up.
app/view/netcreatesource filesapp/view/netcreatesource filesremove all console errors and lingering debug statementsremove obsolete code modulesremove deprecated code from sourceTESTING
There should be no functional changes. To test:
devbranch and see if the problem goes awaySCOPE OF CHANGES
The vast bulk of this work was comment style and section order so they adhere to our code style. Additionally, a few code blocks were rewritten to remove the lint warnings and errors that litter the source code.
NEXT STEPS
It is likely that we will need to replace key parts of our build system with a completely different package, as the current one (brunch) is no longer supported. This is a chance to also migrate parts of the system to typescript, which will help with stricter data modeling discipline.
Before we start adding new systems with the updated module structure, we need to update the build tools and complicated packages like react to work on the modern servers. This is a tricky upgrade that will require all developers to confer, so punting it for now.
Lastly we want to remove obsolete code because it wastes our time by cluttering up the source and obscures the actual function of the application. Like the react package update, this will require all developers to confer and confirm what is in use.