-
Notifications
You must be signed in to change notification settings - Fork 4
Restructured spaghetti code to fix #17 #64
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
base: main
Are you sure you want to change the base?
Conversation
…dex-file Restructured spaghetti code to fix numbbo#17
|
Why do we get the above conflicts? |
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.
This is the line mentioned in the issue #17 (line no 499) which gets called repeatedly by the old architecture.
We removed this line and replaced it with a function which changes the architecture.
The function to this new line is imported in line 17.
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.
We used a venv for testing.
This can be removed if necessary
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.
I don't exactly understand the causal link between these two.
In any case, you should rebase your branch on the current main branch, resolve possible conflicts, and update the pull request.
As part of DSBA open-source contribution project held by Prof.Dimo
We have attempted to fix issue #17
This architectural change makes the code more modular and manageable AND lead to a decrease in latency by 5.8%
But this is not the best solution. Ideally, it would be best to re-write the UI in vue/react to allow dynamic changes as per data