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
Cleaning up unused frontend code from previous search. #7338
Conversation
5716c6f
to
b39ee5b
Compare
This is required now that the `WidgetsStore` which was importing node types through a comment was removed. Instead of importing the types in the `SearchStore` through a comment again, this change is now adding the `node` types explicitly to the TS config files.
a7ac7d7
to
a16c7ba
Compare
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.
looks great to me! everything appears to be working as expected.
@linuspahl since this is a large code delete, could you take a second look and merge when you're happy?
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.
Looks very good! Could not find any problems, not in the main frontend nor the frontend documentation.
This PR is cleaning up the frontend and removes now unused code. The removed code belongs mainly to the pre-3.2 search code which has been replaced now. In addition, I analyzed the frontend build, compared the list of included files to the list of existing files and removed components/modules/css files which have become orphaned.
In a single case (the
TrafficGraph
component), a code change was required to replace the usage of theLegacyHistogram
component with a usage of theGenericPlot
component.Giant list of issues the new search fixes:
As this PR is symbolically concluding the renovation of the search functionality (although we are continuously improving the search experience by adding new features, reimplement missing ones and fixing bugs), it is a good milestone to include a list of issues the new search fixes, which are not addressed by a specific single other PR:
Fixes #520.
Fixes #1844.
Fixes #4822.
Fixes #4836.
Fixes #4900.
Fixes #4955.
Fixes #5060.
Fixes #5065.
Fixes #5137.
Fixes #6071.
Fixes #6073.
Fixes #6110.
Fixes #6114.
Fixes #6140.
Fixes #6516.
Fixes #6598.
Fixes #6619.
Fixes #6628.
Fixes #6660.
Fixes #6734.
Fixes #6759.
Fixes #6809.
Types of changes