-
Notifications
You must be signed in to change notification settings - Fork 641
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
Single responsibility principle for the SchemaView and DataGridView #7884
Comments
connection' dialog (QueryTool). (Reference: pgadmin-org#7884)
All issues are fixed in the PR [#7910]. |
* Show the icon for the 'Reset' button. (Reference #7884) * Reload the server list after connecting to a server in the 'New connection' dialog (QueryTool). (Reference: #7884) * Pass the grid path during the bulk update (click on a radio action) * Don't assign the cell value to the 'rowValue' variable.
is loaded asynchronously, and variable types data may not be available while rendering the 'value' cell. (Fixes pgadmin-org#7884)
New Connection Dialog: Role list is empty |
Filtered rows for a table don't have the initial focus when it opens. |
Table>Constraints>Foreign key>Columns>Referencing dropdown is empty after selecting References dropdown. This is for Table object and ERD tool table dialog. |
Fixed in the PR [7942] |
This issue is fixed in PR, #7944 |
This issue is fixed in PR, #7944 |
This issue is fixed in PR. #7944 |
Tested and verified on candidate build: https://developer.pgadmin.org/builds/2024-09-20-1/ |
Single responsibility principle
improves the code maintainability, because:Current implementation of the
SchemaView
andDataGridView
is amazing. It is great piece of code, and does the job well.But - at the same time, it's not easy to understand, and it is not easy to make change in it, as it could result into breaking other places as well.
When working on the 'useSchemaState' custom hook, I realised that - it is not easy or enough to move some piece of the code and introduce it as the custom hook, the current javascript and feature test-suites have definitely informed me about the broken state at a particular point of time. it made me realised that it won't be easy to introduce new features or do modification in future.
As a result - I would like to propose to use the single responsibility principle for them.
Note: There are still some exceptions in the currently proposed patch.
References:
The text was updated successfully, but these errors were encountered: