Skip to content
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

Fixes filename column width in dataset page #2154

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

luistoptal
Copy link
Collaborator

Pull request for issue: #1119

This PR should fix the issue with very long filenames in the dataset files table
Screenshot from 2025-01-01 09-58-31

How to test?

How have functionalities been implemented?

  • fixed the filename column width to 20ch

Any issues with implementation?

--

Any changes to automated tests?

--

@luistoptal luistoptal marked this pull request as ready for review January 2, 2025 14:54
@kencho51
Copy link
Contributor

kencho51 commented Jan 6, 2025

Hi @luistoptal,

question Shouldn't we suppose to fix that if the file name is longer then 100, the whole file name can still be showed? As even I checked out the develop branch, and the text is actually already wrapped:
image
suggestion: Is it possible to make the column width can be dragged by user manually?
issue: The acceptance criteria is to allow name is longer than 100 characters, the File_name field is still hardcoded as max 100, no more text would be allowed if longer than 100, you can test at http://gigadb.gigasciencejournal.com/adminFile/update/id/17680
suggestion: Remove this required option, so there will be no limit on the file name's length.

@luistoptal
Copy link
Collaborator Author

the text is actually already wrapped

If the filename is one single word without breaks then the text was not wrapped

Is it possible to make the column width can be dragged by user manually?

It is possible to make the columns resizeable with javascript. I believe very long file names is rather a fringe use case. I am not sure allowing users to change column width is an effective solution. I believe wrappign might be enough. However we can make column width draggable. Can you confirm we want this behavior? The ticket does mention either wrapping or allowing draggable column width. I think if the goal is for the user to be able to read the complete file name, wrapping is better because it does not require user interaction. Also the user might click on the header and sort the column instead by mistake if they try to drag

As for the 100 char length. I assumed the issue is that despite the limitation to 100 length, still some files were longer than that and the UI should not assume all files will be capped at 100 chars

Do we actually want to enable filenames longer than 100 chars?

@only1chunts
Copy link
Member

only1chunts commented Jan 6, 2025

I'm have created another ticket (#2170) for the not allowing >100char feature (as suggested in the addfitional infor in #1119 )so for this ticket we can focus on the display. I like the fixed column width with filename wrapping for the reasons Luis outlines.

Copy link
Contributor

@kencho51 kencho51 left a comment

Choose a reason for hiding this comment

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

Hi @luistoptal,

Given all my questions have been addressed, will be happy to approve after the merge conflicts have been fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Tasks To Do
Development

Successfully merging this pull request may close these issues.

3 participants