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

Truncate overly long suggest fields before persisting them #563

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

blmage
Copy link

@blmage blmage commented Feb 10, 2022

The constraint field from the organization_package_link table is limited to 255 chars.

Currently, synchronization fails for packages that use suggest fields longer than 255 chars, and it becomes impossible to manage them from the UI (even if only to remove them).

Note that I am open to suggestions on how we might otherwise handle these cases.

The `constraint` field from the `organization_package_link` table is limited to 255 chars.

Currently, synchronization fails for packages that use `suggest` fields longer than 255 chars, and it becomes impossible to manage them from the UI (even if only to remove them).
@codecov
Copy link

codecov bot commented Feb 10, 2022

Codecov Report

Merging #563 (f64850a) into master (93a82eb) will decrease coverage by 0.01%.
The diff coverage is 50.00%.

Impacted file tree graph

@@             Coverage Diff              @@
##             master     #563      +/-   ##
============================================
- Coverage     99.21%   99.20%   -0.02%     
- Complexity     1893     1894       +1     
============================================
  Files           301      301              
  Lines          6014     6016       +2     
============================================
+ Hits           5967     5968       +1     
- Misses           47       48       +1     
Impacted Files Coverage Δ
...ackageSynchronizer/ComposerPackageSynchronizer.php 96.21% <50.00%> (-0.72%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 93a82eb...f64850a. Read the comment docs.

@alamirault
Copy link
Contributor

Truncated description is not a problem ?

We can maybe change type in database in order to allow longest text ? And manage length in UI ? (css, ellipsis or something else)

@akondas
Copy link
Member

akondas commented Mar 8, 2022

agree with @alamirault, you'd better change the field type to text :)

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

Successfully merging this pull request may close these issues.

3 participants