-
Notifications
You must be signed in to change notification settings - Fork 45
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
Feat/cleanup old GWAS UI app code #1231
Feat/cleanup old GWAS UI app code #1231
Conversation
and keep only V2 and the Results viewer app
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work Pieter! I pulled the changes locally and confirmed only one GWAS app remains without causing any obvious errors.
Before merging consider
- Do we want to rename the folder for the application from
GWASV2
toGWAS
now that there's only one GWAS left? - For tickets like this: https://ctds-planx.atlassian.net/browse/VADC-323 should the developer reference this PR to find all the removed storybooks?
- Are there follow up tickets to implement the needed
changes in other deployment related config files
?
@@ -225,21 +225,6 @@ | |||
"react/no-unused-prop-types": "off" | |||
} | |||
}, | |||
{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Comment, no changes needed:
This was probably a bad approach to begin with. Better would have been to ignore the line or the entire file rather than adding a new global rule for one file.
Good point, although it is probably best to think of a more unique name, maybe GWASApp. Also, with "GWASV2" string having 162 hits in 37 files, this might be a bit large of a change to include here on top of all the other changes. I would prefer to do this in a separate action. There are some more cleanup actions that need to take place, e.g. the
I've update the description with links to the other related PRs |
Jira Ticket: VADC-399
Improvements
Deployment changes