plugins/packages/snowflake/lib/index.ts:1

• The arguments passed to getConnection are mis-ordered: the third parameter is already checkCache, but true is being passed there and the real checkCache is being passed as dataSourceId. This will force caching on, corrupt the cache key, and shift dataSourceId/dataSourceUpdatedAt/context into the wrong slots. Pass checkCache as the 3rd argument and move dataSourceId to the 4th argument.
  server/src/modules/data-sources/service.ts:1
• The new dataSourceDetails contract uses inconsistent casing/keys (datasourceId, datasourcekind, datasourceUpdatedAt vs dataSourceOptionsEnvironmentId). This makes plugin consumers brittle and increases the chance of runtime mismatches. Standardize on a single naming convention (e.g., dataSourceId, dataSourceKind, dataSourceUpdatedAt, dataSourceOptionsEnvironmentId) and keep it consistent across all fields.
  plugins/packages/common/lib/queryBuilder.ts:1
• Fix typo in comment: 'Emtpy' → 'Empty'.
  plugins/packages/common/lib/queryBuilder.ts:1
• Snowflake upsert treats the row as a MERGE whenever any PK value is present. If only a subset of composite PK columns are provided, the MERGE ON condition will include NULL/empty binds for missing PK parts, which will never match and may lead to unintended inserts with NULL PK fields (or constraint failures). Consider enforcing either: (a) all PK values are absent → INSERT, or (b) all PK values are present → MERGE; otherwise throw a QueryBuilderError indicating which PK columns are missing.
  plugins/packages/bigquery/lib/index.ts:1
• In the refreshToken catch block, error.response.statusCode is accessed without guarding error.response, which can throw and mask the original failure. Also, OAuthUnauthorizedClientError is being constructed with error (an object) where a string message is expected. Use optional chaining/guards for error.response and pass a string message (e.g., error.message or a formatted response body) consistently.
  plugins/packages/bigquery/lib/index.ts:1
• QueryError appears to be constructed as (title, message, details), but the message argument is {} here. This will produce an unhelpful message (or a type mismatch) and makes error handling inconsistent. Replace the {} with a descriptive string (e.g., 'BigQuery refresh response did not include access_token').
  plugins/packages/bigquery/lib/index.ts:1
• When oauth_type is tooljet_app, other codepaths (authUrl/accessDetailsFrom/refreshToken) switch to env-based client ID/secret, but buildConnection always uses sourceOptions.client_id/client_secret. This can create an OAuth client with missing/incorrect credentials. Align buildConnection with the same oauth_type branching to use process.env.GOOGLE_CLIENT_ID/GOOGLE_CLIENT_SECRET for the ToolJet app flow.
  plugins/packages/bigquery/lib/index.ts:1
• When datasetId is not provided, this fetches tables for every dataset in parallel and then paginates in-memory. This can be very slow and can hit API rate limits on projects with many datasets/tables. Prefer requiring a datasetId for table listing, or implement server-side pagination (where possible) and/or concurrency limiting (e.g., a small pool) to avoid unbounded parallel requests.
  plugins/packages/bigquery/lib/index.ts:1
• This uses global fetch, which may not be available depending on the Node runtime used for plugins. Since this file already depends on got, consider using got here (or importing a fetch polyfill) to avoid runtime failures in environments without global fetch.
  frontend/src/AppBuilder/Widgets/MultiselectV2/MultiselectV2.jsx:1
• With maxLimit set, selecting the 'Select all' pseudo-option no longer selects all items—it selects only the first N via applyLimit(selectOptions), but the UI label still reads 'Select all …'. This is confusing and can lead to incorrect user expectations. Consider disabling the 'Select all' option whenever maxSelectionLimit is set, or change the label/behavior to clearly indicate it will only select up to the configured limit.
  frontend/src/AppBuilder/Widgets/NewTable/_components/DataTypes/adapters/ButtonColumnAdapter.jsx:1
• This change removes the previous defaulting logic for outline buttons (where a default border color was applied when using the default border settings). Now borders will only render if borderColor is explicitly provided, which can regress styling for outline buttons relying on defaults. Consider restoring the computed default border-color behavior (especially for isOutline) while still honoring an explicit borderColor override.