-
Notifications
You must be signed in to change notification settings - Fork 85
refactor the ´compare´ tool #363
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
Comments
Hi @andlaus |
sure, that would be much appreciated. if you're looking for a place to start, a great one would to refactor the code to making use of dataclasses in order to make it easier to understand what data is expected/available where and to get rid (or at least reduce the number) of |
Ok @andlaus Thanks for the info, Let me check the code first |
Hi @andlaus Status: I am working on implementing the Thanks |
as I see it, #393 is a great first step, but IIRC there are still a few issues lurking, e.g. using two lists which must be of the same size instead of a single list with objects that contain two attributes (for the removed and added diagcomms of a set of diag layers?) . I have to go over the latest version of the code to come to a definitive conclusion, though. |
the code of the
compare
tool currently is a bowl of spaghetti with sub-optimal type annotations (lots oftype: ignore
comments) and desperately needs a cleanup.The text was updated successfully, but these errors were encountered: