test: change suite to emulate UI

[dstala]

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

Summary by CodeRabbit

• Refactor
  • Updated certain column properties for consistency across default and custom columns.

[coderabbitai]

Walkthrough

Walkthrough

The recent update focuses on standardizing certain column properties within the NocoDB project. Specifically, it ensures the system property is consistently set to true for a range of default and custom columns, signifying their importance or special role within the system. Moreover, it adopts a uniform naming convention for the column_name property by changing it from 'Id' to 'id', reflecting a preference for lowercase identifiers across different column types.

Changes

Files	Change Summary
.../factory/column.ts	Updated system property to true and column_name from 'Id' to 'id' for various columns.

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>.
  • Generate unit-tests 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 tests 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 1ec1745 and a1a5ca9.

Files selected for processing (1)

• packages/nocodb/tests/unit/factory/column.ts (8 hunks)

Additional comments: 8

packages/nocodb/tests/unit/factory/column.ts (8)

• 31-31: The system property is explicitly set to true for the created_at column. This change aligns with the PR objectives to standardize column properties. However, ensure that this property's explicit setting is necessary and consistent with the application's data model and testing requirements.
• 45-45: Similar to the previous comment, the system property is set to true for the updated_at column. It's good practice to maintain consistency in column properties, especially for system-generated timestamps. Confirm that this setting aligns with the intended use of these columns in tests and the broader application.
• 56-56: The column_name property is updated from 'Id' to 'id' for the id column in the textBased custom columns. This change is part of the effort to standardize column naming conventions. It's important to ensure that this change is reflected across all tests and related code to avoid potential issues with case sensitivity in database operations or UI display logic.
• 89-89: The column_name property is updated from 'Id' to 'id' for the id column in the numberBased custom columns. As with the previous changes, ensure that this standardization is consistently applied and tested across the application to prevent any unintended consequences.
• 127-127: The column_name property is updated from 'Id' to 'id' for the id column in the dateBased custom columns. Consistency in naming conventions is crucial, especially when dealing with date and time-related data. Verify that this change is accurately reflected in all relevant areas of the application.
• 145-145: The column_name property is updated from 'Id' to 'id' for the id column in the selectBased custom columns. This change contributes to the overall effort of standardizing column names. Ensure that the impact of this change is thoroughly tested, particularly in scenarios involving selection-based UI components.
• 165-165: The column_name property is updated from 'Id' to 'id' for the id column in the userBased custom columns. This standardization is important for consistency in user-related data handling. Confirm that this change does not affect the functionality of user-based features and is properly tested.
• 182-182: The column_name property is updated from 'Id' to 'id' for the id column in the custom column definition. This change is part of the broader effort to standardize column naming conventions. It's essential to ensure that this change is compatible with any custom functionality that relies on column names and is adequately tested.

[github-actions]

Uffizzi Preview deployment-48994 was deleted.