Sonarly Claude Code
eda347c25e
https://sonarly.com/issue/37129?type=bug Dashboard record-table widgets can reference views that are invisible to other users, so non-admins get empty widgets even when they can read the underlying object records. Fix: Implemented the fix in the backend visibility layer so dashboard table-widget views remain readable across users without changing generic UNLISTED behavior. ### What changed 1. **Adjusted view visibility filtering for table widgets** - **File:** `packages/twenty-server/src/engine/metadata-modules/view/services/view.service.ts` - Updated `isViewVisibleToUser()` to allow: - all `WORKSPACE` views (unchanged) - **`UNLISTED` + `TABLE_WIDGET` views for all workspace users** (new) - all other `UNLISTED` views remain creator-only (unchanged) This ensures `getViews(viewTypes: [TABLE_WIDGET])` returns widget-backed views to shared dashboard users, preventing the downstream `currentView` missing/empty-widget path. 2. **Added integration coverage for regression** - **File:** `packages/twenty-server/test/integration/metadata/suites/view/get-views-table-widget-visibility.integration-spec.ts` - New tests verify that for a non-creator user: - an `UNLISTED` `TABLE_WIDGET` view is returned by `getViews(viewTypes: [TABLE_WIDGET])` - an `UNLISTED` non-widget view (`TABLE`) remains hidden ### Why this layer The bug is caused by backend metadata filtering before frontend widget load. Fixing visibility at `ViewService` is the correct layer and avoids frontend workarounds. ### Validation notes Attempted to run tests/lint, but this worktree does not have install-time dependencies available: - `npx nx lint:diff-with-main twenty-server` failed (Nx modules not installed) - direct jest run failed due missing module resolution in local environment
The #1 Open-Source CRM
Website · 
Documentation · 
Roadmap · 
Discord · 
Figma
Why Twenty
Twenty gives technical teams the building blocks for a custom CRM that meets complex business needs and quickly adapts as the business evolves. Twenty is the CRM you build, ship, and version like the rest of your stack.
Learn more about why we built Twenty
Installation
Cloud
The fastest way to get started. Sign up at twenty.com and spin up a workspace in under a minute, with no infrastructure to manage and always up to date.
Build an app
Scaffold a new app with the Twenty CLI:
npx create-twenty-app my-app
Define objects, fields, and views as code:
import { defineObject, FieldType } from 'twenty-sdk/define';
export default defineObject({
nameSingular: 'deal',
namePlural: 'deals',
labelSingular: 'Deal',
labelPlural: 'Deals',
fields: [
{ name: 'name', label: 'Name', type: FieldType.TEXT },
{ name: 'amount', label: 'Amount', type: FieldType.CURRENCY },
{ name: 'closeDate', label: 'Close Date', type: FieldType.DATE_TIME },
],
});
Then ship it to your workspace:
npx twenty deploy
See the app development guide for objects, views, agents, and logic functions.
Self-hosting
Run Twenty on your own infrastructure with Docker Compose, or contribute locally via the local setup guide.
Everything you need
Twenty gives you the building blocks of a modern CRM (objects, views, workflows, and agents) and lets you extend them as code. Here's a tour of what's in the box.
Want to go deeper? Read the 
User Guide for product walkthroughs, or the Documentation for developer reference.
|
|
|
|
|
|
Learn more about version control in docStack
TypeScript
Nx
NestJS, with BullMQ, 
PostgreSQL, 
Redis
React, with Jotai, Linaria and Lingui
Thanks
Thanks to these amazing services that we use and recommend for UI testing (Chromatic), code review (Greptile), catching bugs (Sentry) and translating (Crowdin).
Join the Community
Star the repo · Discord · 
Feature requests · Releases · 
X · 
LinkedIn · 
Crowdin · 
Contribute