8000 Nc fix/misc UI changes by rameshmane7218 · Pull Request #9829 · nocodb/nocodb · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Nc fix/misc UI changes #9829

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

Merged
merged 3 commits into from
Nov 16, 2024
Merged

Nc fix/misc UI changes #9829

merged 3 commits into from
Nov 16, 2024

Conversation

rameshmane7218
Copy link
Member

Change Summary

Provide summary of changes with issue number if any.

Change type

  • feat: (new feature for the user, not a new feature for build script)
  • fix: (bug fix for the user, not a fix to a build script)
  • docs: (changes to the documentation)
  • style: (formatting, missing semi colons, etc; no production code change)
  • refactor: (refactoring production code, eg. renaming a variable)
  • test: (adding missing tests, refactoring tests; no production code change)
  • chore: (updating grunt tasks etc; no production code change)

Test/ Verification

Provide summary of changes.

Additional information / screenshots (optional)

Anything for maintainers to be made aware of

@rameshmane7218 rameshmane7218 self-assigned this Nov 15, 2024
@dosubot dosubot bot added the size:S This PR changes 10-29 lines, ignoring generated files. label Nov 15, 2024
Copy link
Contributor
coderabbitai bot commented Nov 15, 2024
📝 Walkthrough
📝 Walkthrough

Walkthrough

The changes in this pull request involve modifications to the user interface of two Vue components: DataSources.vue and UIAcl.vue. In DataSources.vue, the tab label has been updated from "UI ACL" to "View Access". In UIAcl.vue, the tooltip text and placeholder for the search input have been updated to improve clarity and localization. The underlying logic and functionality of both components remain unchanged, with no new methods or properties introduced.

Changes

File Path Change Summary
packages/nc-gui/components/dashboard/settings/DataSources.vue Updated tab label from "UI ACL" to "View Access". No changes to functionality or logic.
packages/nc-gui/components/dashboard/settings/UIAcl.vue Updated tooltip text and search input placeholder for better clarity and localization. No changes to functionality or logic.

Possibly related PRs

  • fix: ui acl issue #8916: This PR modifies the UIAcl.vue component, which is closely related to the changes made in DataSources.vue regarding user interface elements and their labels.
  • Nc fix/field modal issues #8653: Although primarily focused on field modals, this PR also involves UI changes that may relate to the overall user experience in the dashboard settings, similar to the changes in DataSources.vue.
  • fix(nc-gui): allow user to submit form in locked view #9705: This PR addresses form submission logic in Form.vue, which may indirectly relate to the UI changes in DataSources.vue as both involve user interactions within the dashboard settings.

Suggested labels

👓 Scope : View, size:XS, lgtm

Suggested reviewers

  • DarkPhoenix2704
  • dstala

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 632f200 and 3ad875e.

⛔ Files ignored due to path filters (1)
  • packages/nc-gui/lang/en.json is excluded by !**/*.json
📒 Files selected for processing (2)
  • packages/nc-gui/components/dashboard/settings/DataSources.vue (1 hunks)
  • packages/nc-gui/components/dashboard/settings/UIAcl.vue (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
  • packages/nc-gui/components/dashboard/settings/DataSources.vue
  • packages/nc-gui/components/dashboard/settings/UIAcl.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
🪧 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 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.

@dosubot dosubot bot added the 🐛 Type: Bug Something is broken or incorrect unexpectedly. label Nov 15, 2024
Copy link
Contributor
@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Outside diff range and nitpick comments (1)
packages/nc-gui/components/dashboard/settings/UIAcl.vue (1)

Line range hint 3-3: Consider type safety and documentation improvements.

  1. Consider using the Role type consistently instead of string literals:
-const roles = ref<string[]>(['editor', 'commenter', 'viewer'])
+const roles = ref<Role[]>(['editor', 'commenter', 'viewer'])
  1. Consider replacing the inline comment with proper JSDoc for the saveUIAcl function:
+/**
+ * Saves the UI access control settings for tables
+ * Updates the visibility settings for modified tables and shows a success message
+ */
 async function saveUIAcl() {

Also applies to: 13-13, 89-89

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 10ca6c8 and 632f200.

⛔ Files ignored due to path filters (1)
  • packages/nc-gui/lang/en.json is excluded by !**/*.json
📒 Files selected for processing (2)
  • packages/nc-gui/components/dashboard/settings/DataSources.vue (1 hunks)
  • packages/nc-gui/components/dashboard/settings/UIAcl.vue (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • packages/nc-gui/components/dashboard/settings/DataSources.vue

@@ -150,7 +150,7 @@ const columns = [
<div class="w-full h-full flex flex-col">
<NcTooltip class="mb-4 first-letter:capital font-bold max-w-100 truncate" show-on-truncate-only>
<template #title>{{ base.title }}</template>
<span> UI ACL : {{ base.title }} </span>
<span> {{ $t('labels.viewAccess') }} : {{ base.title }} </span>
Copy link
Contributor

Choose a reason for hiding this comment

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

💡 Codebase verification

Translation key needs to be added to other language files

The translation key labels.viewAccess is only present in the English locale file (en.json) but missing from all other language files. This could lead to missing translations for non-English users.

  • Add the labels.viewAccess translation key to all language files under packages/nc-gui/lang/
  • Currently only exists in: packages/nc-gui/lang/en.json
🔗 Analysis chain

LGTM! Verify translation key exists.

The change improves i18n support by using the translation function for "View Access" text, which aligns with the terminology update across the UI.

Let's verify the translation key exists:

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check if the 'labels.viewAccess' translation key exists in the localization files

# Search for the translation key in all locale files
rg -g '*.json' '"labels.viewAccess"' packages/nc-gui/lang/

Length of output: 60


Script:

#!/bin/bash
# Let's try a broader search to:
# 1. Find all JSON files in the lang directory
# 2. Look for any keys containing "viewAccess" (case insensitive)
# 3. Look for similar translations that might be using a different key

# List all JSON files in lang directory
echo "=== JSON files in lang directory ==="
fd -e json . packages/nc-gui/lang/

# Search for any keys containing viewAccess (case insensitive)
echo -e "\n=== Keys containing 'viewAccess' (case insensitive) ==="
rg -i "viewaccess" packages/nc-gui/lang/

# Search for similar translations that might use a different key
echo -e "\n=== Similar translations ==="
rg -i "\"view.*access\"" packages/nc-gui/lang/

Length of output: 1713

Copy link
Contributor
github-actions bot commented Nov 15, 2024

Uffizzi Preview deployment-58288 was deleted.

@o1lab o1lab force-pushed the nc-fix/misc-ui-changes branch from 632f200 to 3ad875e Compare November 16, 2024 07:43
@dosubot dosubot bot added the lgtm This PR has been approved by a maintainer label Nov 16, 2024
@dstala dstala merged commit 6de41d2 into develop Nov 16, 2024
19 of 22 checks passed
@dstala dstala deleted the nc-fix/misc-ui-changes branch November 16, 2024 08:02
@coderabbitai coderabbitai bot mentioned this pull request Dec 14, 2024
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm This PR has been approved by a maintainer size:S This PR changes 10-29 lines, ignoring generated files. 🐛 Type: Bug Something is broken or incorrect unexpectedly.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0