8000 Upgrade to 301.x by TheRushingWookie · Pull Request #13206 · nocodb/nocodb · GitHub
[go: up one dir, main page]

Skip to content

Upgrade to 301.x#13206

Open
TheRushingWookie wants to merge 30 commits intonocodb:developfrom
githubuserrobot:301.x
Open

Upgrade to 301.x#13206
TheRushingWookie wants to merge 30 commits intonocodb:developfrom
githubuserrobot:301.x

Conversation

@TheRushingWookie
Copy link

No description provided.

YUsernameNoWin and others added 29 commits December 16, 2025 00:05
AutoNumber columns should use NULL checks instead of empty-string
comparisons to avoid bigint cast errors in aggregate queries.
Use schema-qualified table paths for m2m relations so
Postgres queries don’t reference missing relations.
Build WHERE clauses for formula fields from their SQL
expressions to avoid referencing non-existent columns.
…null-checks

fix: treat AutoNumber as numeric in aggregates
- Add ColumnRoleVisibility model with CRUD operations
- Create database migration for nc_column_role_visibility_v2 table
- Implement column visibility service and controller for API endpoints
- Add ACL permissions restricting column visibility management to owners
- Modify data query enforcement to hide columns based on user roles
- Create ColumnUIAcl.vue component for managing column visibility in UI
- Update globals.ts and module registration

This feature allows owners to hide specific columns from editor, commenter, and viewer roles at the table level, providing fine-grained access control over sensitive data.
@CLAassistant
Copy link
CLAassistant commented Mar 9, 2026

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
0 out of 3 committers have signed the CLA.

❌ YUsernameNoWin
❌ bferris1
❌ TheRushingWookie
You have signed the CLA already but the status is still pending? Let us recheck it.

- Add ColumnRoleVisibility model with CRUD operations
- Create database migration for nc_column_role_visibility_v2 table
- Implement column visibility service and controller for API endpoints
- Add ACL permissions restricting column visibility management to owners
- Modify data query enforcement to hide columns based on user roles
- Create ColumnUIAcl.vue component for managing column visibility in UI
- Update globals.ts and module registration

This feature allows owners to hide specific columns from editor, commenter, and viewer roles at the table level, providing fine-grained access control over sensitive data.
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.

4 participants

0