Feature: Table redesign

[AkashJana18]

• What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
  Changed hover effect, added search bar in 2 pages and added button as per requirement.

• Why was this change needed? (You can also link to an open issue here)
  Fixes: 🚀 Feature: Table redesign #1286

• Other information:
  
  

[vercel]

@AkashJana18 is attempting to deploy a commit to the Arc53 Team on Vercel.

A member of the Team first needs to authorize it.

[ManishMadan2882]

Hi @AkashJana18,
Just reviewed, have few points:

• Make sure the UI matches the figma
• The Add new button triggers the Upload modal
• Search bar filters documents depending on document name
  Also try to sync with main as there some tab design related changes in this file from your previous PR.
  Thanks!

[AkashJana18]

Hey @ManishMadan2882 the required changes are made can you please check it out.
Feel free to ask for more changes if required :)

[ManishMadan2882]

Hi @AkashJana18
Have few points:

1. There is an app crash on creating a new API Key
2. When the modal opens on clicking the New Document button, it partially covers the screen
   
3. For table re-design, please follow figma, but you can ignore pagination for now as it will need few endpoints.
4. Also, please sync your branch with upstream main, there are conflicts.
   Thanks!

[dartpain]

Hey @AkashJana18 how is it going?

[AkashJana18]

@dartpain working on it PR will updated soon

[AkashJana18]

Hey @ManishMadan2882 I have made the required changes

1. Can you specify the kind of app crash on creating new key?
2. Also can guide me regarding resolving conflict. Like do i need to keep the skeleton reloader or remove it?

[ManishMadan2882]

Hi @AkashJana18

1. The app crashes on creating new api key
   The error is logged in the console
   Uncaught TypeError: Cannot read properties of undefined (reading 'toLowerCase') at APIKeys.tsx:93:20
2. We need to keep every change in the main branch including the skeleton.
   Thanks.

[AkashJana18]

Hey @ManishMadan2882 conflicts have been resolved.
Can you please check if the apikey error is resolved or not.
Thank you.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 33.45%. Comparing base (67a97a7) to head (d18cb37).
Report is 11 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1300   +/-   ##
=======================================
  Coverage   33.45%   33.45%           
=======================================
  Files          64       64           
  Lines        3273     3273           
=======================================
  Hits         1095     1095           
  Misses       2178     2178           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[ManishMadan2882]

Hey @AkashJana18
Do you mind testing these changes before pushing or is there any issue you are facing during set up on your system?

Fails with npm run dev

[plugin:vite:react-babel] /home/manish/Documents/contributors/akash jana/DocsGPT/frontend/src/settings/APIKeys.tsx: Unexpected token, expected "," (57:6)
  60 |       });
/home/manish/Documents/contributors/akash jana/DocsGPT/frontend/src/settings/APIKeys.tsx:57:6
55 |            );
56 |          }
57 |        })
   |        ^
58 |        .catch((error) => {
59 |          console.error(error);

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
docs-gpt	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 23, 2024 9:59pm

[AkashJana18]

@ManishMadan2882 how do i revert the changes made while resolving conflict. I think i made error while resolving conflict if you can revert the change in APIkeys.tsx i can fix it.
i resolved conflict from github itself (not from vscode).

[ManishMadan2882]

First revert your merge commit, then Follow this on VSC

[ManishMadan2882]

Perfect, Thanks @AkashJana18