Skip to content

[Enhancement] - Issue-682/create documents route - #683

Merged
leekahung merged 5 commits into
Developmentfrom
issue-682/create-documents-route
Nov 1, 2024
Merged

[Enhancement] - Issue-682/create documents route#683
leekahung merged 5 commits into
Developmentfrom
issue-682/create-documents-route

Conversation

@leekahung

Copy link
Copy Markdown
Contributor

This PR:

Resolves #682 and migrates Documents list from Profile to new Documents page and re-purpose Documents list for contacts using state management.

Screenshots (if applicable):

Screen.Recording.2024-10-09.at.5.09.14.PM.mov

…e contact documents list; Created new route for new Documents page

Co-authored-by: Jared Krajewski <krajewski.jared@gmail.com>
@leekahung leekahung added the refactor/optimization General label for refactoring, optimizing, or reorganizing codebase label Oct 10, 2024

@andycwilliams andycwilliams left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seeing some oddities with Shared Profile with resizing and overlapping elements.

Small screen (this happens when I resize the screen when on a shared profile. But doesn't seem to if I'm already on a mobile view on Contacts and then go to a shared profile):
2024-10-09 (1)

Medium screen (placeholder documents table also cuts off at the bottom):
2024-10-09 (2)

Large screen:
2024-10-09

Also maybe the placeholder text for shared profiles should be something more like "No documents have been shared with you. Any that are shared will appear here".

Other thoughts, likely for another PR. I think we should style the Documents and Contacts mobile versions more consistently. The Share/Add buttons are not spaced from the screen sides the same way. It also looks like the text in Documents is bolded.

2024-10-09 (5)

2024-10-09 (4)

Similarly, for the desktop versions, we should probably center the Add Contact button since we're centering the buttons for Documents now.

@leekahung

Copy link
Copy Markdown
Contributor Author

With the main problem with the issue resolved, think we can open up a new PR to handle all the styling corrections.

@Jared-Krajewski

Jared-Krajewski commented Oct 25, 2024

Copy link
Copy Markdown
Contributor

With the main problem with the issue resolved, think we can open up a new PR to handle all the styling corrections.

yeah, I think that sounds good. Is that good with you @andycwilliams ?

@andycwilliams andycwilliams left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

375178745-a7b25bc1-12bc-4067-a461-36ca69dfaa2c

375178749-e4efa5f7-8bdf-4d67-a646-433f01f4ee81

This strange responsivity is still occurring. I'm not comfortable show this to a prospective investor. We want to put our best foot forward.

There's other tidying that could be done but I would really like this to be addressed.

Comment thread src/pages/Documents.jsx
import { DocumentTable } from '@components/Documents';
import { Container } from '@mui/system';

const Documents = () => {

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No JSDocs?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Given it's a page and not exactly a component, didn't think it'll be necessary to write one, but I can include a short documentation

Comment thread src/pages/Documents.jsx Outdated
import { DocumentListContext } from '@contexts';
import { truncateText } from '@utils';
import { DocumentTable } from '@components/Documents';
import { Container } from '@mui/system';

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a reason Container is imported from '@mui/system' rather than '@mui/material' like it is elsewhere?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No reason, it looks like the import path auto completed to the wrong path

I'll change it back

@leekahung

leekahung commented Oct 31, 2024

Copy link
Copy Markdown
Contributor Author

375178745-a7b25bc1-12bc-4067-a461-36ca69dfaa2c

375178749-e4efa5f7-8bdf-4d67-a646-433f01f4ee81

This strange responsivity is still occurring. I'm not comfortable show this to a prospective investor. We want to put our best foot forward.

There's other tidying that could be done but I would really like this to be addressed.

Which is why I recommend fixing this in a quick follow-up with this PR being the main push for component changes.

Currently working on those styling fixes in a local branch, as stated in an earlier comment about styling corrections. I've just pushed it up as a PR (see PR #684)

@andycwilliams andycwilliams left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Think it's good practice to address things like the responsivity issue. But since another PR is up now I'm more okay with approving this.

@leekahung

leekahung commented Nov 1, 2024

Copy link
Copy Markdown
Contributor Author

Think it's good practice to address things like the responsivity issue. But since another PR is up now I'm more okay with approving this.

Don't think it's bad practice to have dedicated PRs for specific issues at hand, one with the main feature update, and then a follow-up to address bugs, unless the initial PR features breaks functionality. This is merging to the Development branch and not the Main/Master branch just yet where it's used for deployment.

@leekahung
leekahung merged commit 6f49b99 into Development Nov 1, 2024
@leekahung
leekahung deleted the issue-682/create-documents-route branch November 8, 2024 04:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

refactor/optimization General label for refactoring, optimizing, or reorganizing codebase

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Enhancement] - Create My Documents View

3 participants