Fix screen large items

[webysther]

What type of PR is this?

feature

What this PR does / why we need it:

improve list items on large screen
change the default pageSize to 30 because is Least common multiple of 2, 3 and 5.

Which issue(s) this PR fixes:

Closes #469

Before:

After:

Summary by CodeRabbit

• UI Improvements
  • Expanded container maximum width to provide more screen real estate
  • Enhanced item listing grid layout to display 5 columns on large screens, improving responsiveness and item visibility

[coderabbitai]

Walkthrough

The pull request modifies the layout configurations in two components: Container.vue and items.vue. In Container.vue, the maximum width class is updated from max-w-6xl to max-w-7xl, which adjusts the container's width. In items.vue, the pageSize variable is changed from 21 to 30, and the grid layout is enhanced by adding a fifth column for larger screens, thereby improving the display of items on wider viewports.

Changes

File	Change Summary
frontend/components/Base/Container.vue	Updated max-w-6xl to max-w-7xl class
frontend/pages/items.vue	Changed pageSize from 21 to 30 and added lg:grid-cols-5 to grid layout

Assessment against linked issues

Objective	Addressed	Explanation
Show more columns on 4k screen [#469]	✅

Possibly related PRs

• Fix picture attachment modal (buttons cropped) #239: The changes in frontend/pages/item/[id]/index.vue involve modifications to the HTML structure and CSS classes, which may relate to layout adjustments similar to the changes made in Container.vue regarding component appearance.
• feat: display item labels in the details page #387: The modifications in frontend/pages/item/[id]/index.vue include adding a new section for displaying labels, which may involve layout considerations that could be relevant to the changes in Container.vue.

Suggested reviewers

• tankerkiller125

Security Recommendations

🔒 Security Insights:

1. Ensure responsive design changes do not introduce layout-based vulnerabilities.
2. Validate that grid column expansion does not expose sensitive UI elements.
3. Verify that responsive breakpoints do not create unexpected rendering paths.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7276fed and 0dd26fe.

📒 Files selected for processing (1)

• frontend/pages/items.vue (2 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• frontend/pages/items.vue

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[webysther]

Come on, folks, this is a no-brainer... :)

[tankerkiller125]

Lint must pass before we can merge (we are ignoring the failed PR builds at this moment)

[katosdev]

Come on, folks, this is a no-brainer... :)

Hey! Apologies for the delays on this one, work has been quite manic of late, including some very long hours.
We appreciate your patience.

Are you able to review the linting errors as @tankerkiller125 has pointed out, and we'll get this one tested and merged @webysther ?

[webysther]

Come on, folks, this is a no-brainer... :)

Hey! Apologies for the delays on this one, work has been quite manic of late, including some very long hours. We appreciate your patience.

Are you able to review the linting errors as @tankerkiller125 has pointed out, and we'll get this one tested and merged @webysther ?

No, I need to build again, looks like this link is not related to my code, I think this linter run on the file that have changes wich sounds strange but I will fix that, give me one day.