You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: DEV_README.md
+33-10
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@
6
6
7
7
<b>`Developer's Read Me`</b>
8
8
9
-
<b>`** v12.0.0 **`</b>
9
+
<b>`** v13.0.0 **`</b>
10
10
11
11
<p>In this version our team focused on refactoring the broken code base from all previous versions. </p>
12
12
@@ -16,15 +16,20 @@ Run npm run dev twice if you do not manually run tsc to compile the files first.
16
16
17
17
<p><b> WHAT WE UPDATED: </b></p>
18
18
19
-
<p>1. trimmed dependency issues from 54 down to 1. this one cannot be resolved because it is from the 30 viewers</p>
20
-
<p>2. Broke backend into MVVM/MVC model</p>
21
-
<p>3. Made sure types are enforced in typescript</p>
22
-
<p>4. Fixed import and export local files</p>
23
-
<p>5. Fixed Authentication</p>
19
+
<p>1. Refactored UX/UI to enhance user's performance by streamlining key features</p>
20
+
<p>2. Implemented Query History and selected query will populate on Monaco Editor</p>
21
+
<p>3. Changed from CodeMirror to Monaco Editor to bring back in colors for selected keywords</p>
22
+
<p>4. Reimplemented table rows to display in Table View</p>
23
+
<p>5. Fixed import and export local files for Postgres and MySQL</p>
24
+
<p>6. Fixed Authentication</p>
25
+
<p>7. Added additional testing suites</p>
26
+
<p>8. Introduced layout saving for ERD view</p>
24
27
25
28
<p><b> WHAT NEEDS TO BE DONE: </b></p>
26
29
27
-
<p><b>1. Isolating Database</b> <br> One of the biggest tasks that we tried but <b>did not finish</b> is isolating the concerns of each database type (DBType). The current application has multiple</p>
30
+
<p>1. Refractor tableTabBar </p>
31
+
32
+
<p><b>2. Isolating Database</b> <br> One of the biggest tasks that we tried but <b>did not finish</b> is isolating the concerns of each database type (DBType). The current application has multiple</p>
<p>The road map is finish connecting the siloed pieces for postgres, then moving on to mysql <br><br> <b>***Important*** <br> There is not an entry for this system yet but this file frontend/components/iews/ERTables/ERDisplayWindow.tsx will replace frontend/components/iews/ERTables/ERTabling.tsx when this is ready</b></p>
42
+
<p>The road map is finish connecting the siloed pieces for postgres, then moving on to mysql <br><br> <b>***Important*** <br> There is not an entry for this system yet but this file frontend/components/iews/ERTables/ERDisplayWindow.tsx will be the entry</b></p>
38
43
39
-
<p><b>2. ERD Logic Update</b><br>Currently, previous wrote the frontend to send back a big bundle of all the operations done in the frontend ERD Table. This ERD table object is divided by add, drop, and alter. All the add operations will execute first then drop, then alter. This is <b>BAD</b>. <br><br> We need to redesign frontend to send back "sequental" operations instead of bundling operations by add, drop, alter because it takes care of multiple edge cases and users in the front can do as many operations they want to ensure <b>SAVE</b> works. I illustrated the problem below. The current backend is written out already. We just need to make sure the frontend is send back the appropriate logic</p>
44
+
<p><b>3. ERD Logic Update</b><br>Currently, previous wrote the frontend to send back a big bundle of all the operations done in the frontend ERD Table. This ERD table object is divided by add, drop, and alter. All the add operations will execute first then drop, then alter. This is <b>BAD</b>. <br><br> We need to redesign frontend to send back "sequental" operations instead of bundling operations by add, drop, alter because it takes care of multiple edge cases and users in the front can do as many operations they want to ensure <b>SAVE</b> works. I illustrated the problem below. The current backend is written out already. We just need to make sure the frontend is send back the appropriate logic</p>
<br><br> <b>**_Important_** <br> This is wrtten at backend/src/ipcHandlers/dbCRUDHandlerERD.ts and will replace backend/src/ipcHandlers/dbCRUDHandler.ts when this is ready</b>
44
49
45
-
<p><b>3. Async event emmiters between front/backend</b></p>
50
+
<p><b>4. Async event emmiters between front/backend</b></p>
46
51
<p>Currently, the way the feedback modal works is by handling events that are emitted from both the frontend and the backend. Ideally, this should be refactored to be state dependent rather than event dependent, as it controls the display of the modal. This can be tied into the centralized async event emitter added to frontend/components/app.tsx, in conjunction with migration to reducers from state variables. The goal will be to house modal messages in the store tied to the main app reducer. From there, the async handler can send new messages to the state via main app dispatch, and any other front end feedback can do the same.<br><br>
47
52
The main roadblock in the way of finalizing the transfer of event handlers out of the frontend is the way the dblist (list of databases in the sidebar) gets updated. Many event handlers in the backend send a dblist update event out to update the front end. Ideally, this should be handled by returning the new dblist changes out of the handler and using that resolved value to update state whenever an action would cause a dblist change. Right now, app.tsx has a useEffect running that listens for those dblist updates every frame. This is inefficient as a frontend concern.<br><br>
48
53
The spinner currently works in a similar way to feedback. Once all async is completely migrated (including dblist update changes), this spinner can simply be tied to the loading property in the main app state.<br><br>
@@ -52,3 +57,21 @@ There are still some filesystem read/write calls in the front end. This should b
52
57
<p>5. </p>
53
58
54
59
<p><b> WHAT IS BROKEN: </b></p>
60
+
61
+
<p>1. The application on Windows may periodically crash.</p>
62
+
<p>2. There are import issues on mac computers.</p>
63
+
64
+
- Unable to import pg or mySQL database files
65
+
<p>3. Duplicates appear on previous queries.</p>
66
+
67
+
- In 'queryView', the 'queriesRan' state is defined, set, and passed down as a prop to its child component 'queryHistory'. On line 54 of 'queryHistory', duplicate query saved in the queriesRan state are removed. However, there's a problem: when we click the format button in QuerySqlInput and then run the query, it saves the query again. This happens because the new Set method doesn't recognize the formatted SQL strings due to the presence of '\n' characters. Consequently, clicking the run query button for both unformatted and formatted SQL strings results in duplicates being saved in the query history.
68
+
69
+
<p>4. Label and Group field disappears.</p>
70
+
71
+
- In the queries tab, the Label and Group text in input field will disappear when selecting the Monaco Editor.
72
+
- The bug may arise from the useEffect hook, which triggers every time the component updates. Any changes detected in the editor results in a new Monaco Editor instance, potentially resetting the label and group text inputs.
73
+
74
+
<p>5. Foreign and Primary keys.</p>
75
+
76
+
- Unable to select the primary and/or foreign key of a newly added column until the column is saved onto the database. Once saved onto the database, we can then select the primary and foreign key and save them onto the database.
@@ -76,6 +76,8 @@ To get started on contributing and editing databases to this project:
76
76
- Databases
77
77
78
78
- In the 'DATABASES' view, an interactive Entity Relationship Diagram (`ER DIAGRAM`) is displayed for the selected database.
79
+
- Users can now save table layout in version 13.
80
+
79
81
- Users can select `TABLE` to see selected database in tabular form.
80
82
81
83
- Users can select a table from a list of all the tables in the schema of the currently selected database.
@@ -96,7 +98,7 @@ To get started on contributing and editing databases to this project:
96
98
</div>
97
99
<br>
98
100
99
-
-<strong>NEW</strong> 3D Database Visualization
101
+
- 3D Database Visualization
100
102
- From the 'DATABASES' view, select the '3D View' tab on the far right of the sidebar to launch the brand new 3D database visualizer.
101
103
- Individual table nodes are distinguished by their different colors
102
104
- Column nodes are joined to table nodes and match their source table color
@@ -132,20 +134,19 @@ To get started on contributing and editing databases to this project:
132
134
133
135
- Queries
134
136
135
-
- In the 'QUERIES' view, the main panel is where the query input text field is located, utilizing CodeMirror. The paint button in the top right corner of the panel auto-formats the inputted query.
137
+
- In the 'QUERIES' view, the main panel is where the query input text field is located, utilizing Monaco. The paint button in the top right corner of the panel auto-formats the inputted query.
136
138
- Users can select the database to use in the 'Database' dropdown above the main panel.
137
139
- Users also have the option to execute a labelled/grouped or unlabelled/ungrouped query — simply provide a label/group in the 'Label'/'Group' field above the main panel to identify the query in later comparisons against other queries.
138
140
- Please note that only labelled queries will be saved in the current session for future references.
139
141
- To execute the query, simply select the 'RUN QUERY' button at the bottom of the panel or press 'Ctrl-Enter' on the keyboard.
140
-
- The 11th version now includes the functionality to run multiple queries, allowing users to obtain more reliable testing results.
141
-
<br />
142
+
- Users have the option to run multiple queries, allowing users to obtain more reliable testing results.
143
+
- Version 13 introduces a new feature that enables users to access and view previous queries. Upon selecting a previous query, it populates the query input field, allowing users to make edits before executing.
0 commit comments