You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "alexandrusoare (via GitHub)" <gi...@apache.org> on 2026/02/04 13:23:57 UTC
[PR] fix(scatter): Fix ad-hoc metric for pointsize [superset]
alexandrusoare opened a new pull request, #37669:
URL: https://github.com/apache/superset/pull/37669
### SUMMARY
When creating a deck.gl Scatterplot chart, it's possible to choose between a fixed point size, or a dynamic one (calculated with a metric). The metric popover allows you to either select an existing metric from the dataset, or create a new one via custom SQL. Charts using a custom SQL metric are showing errors.
#### Root Cause
This is a regression from a previous fix that addressed fixed point size not working. That fix introduced `extractMetricKey()` which converts adhoc metric objects to plain strings, losing the `expressionType` property that the backend needs to identify custom SQL metrics.
**What happens:**
1. User creates a custom SQL metric like `count(*) * 1.1`
2. The UI correctly stores it as an object with `expressionType: "SQL"` and `sqlExpression`
3. `extractMetricKey()` strips it down to just the string `"count(*) * 1.1"`
4. Backend receives the string, can't identify it as an adhoc metric (missing `expressionType`), and it's not a saved metric either
5. Error: "Metric does not exist"
#### Fix
Modified `buildQuery.ts` to preserve the full metric object instead of extracting only the label string. Used `getMetricLabel()` only where a string representation is actually needed (for the `orderby` clause).
#### Alternative Considered
**Fix `extractMetricKey()` to optionally return full objects** - This would be a more "correct" fix at the utility level, but touches shared code used by other components, increasing risk of unintended side effects. The minimal fix in `buildQuery.ts` is safer and achieves the same result.
#### Tests Added
5 new tests to prevent future regressions:
- Adhoc SQL metrics (`count(*) * 1.1`)
- Adhoc SIMPLE metrics (`AVG(column)`)
- Deduplication of adhoc metrics
- Fixed type with string values
- Undefined metric values
### BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
<!--- Skip this if not applicable -->
### TESTING INSTRUCTIONS
<!--- Required! What steps can be taken to manually verify the changes? -->
### ADDITIONAL INFORMATION
<!--- Check any relevant boxes with "x" -->
<!--- HINT: Include "Fixes #nnn" if you are fixing an existing issue -->
- [ ] Has associated issue:
- [ ] Required feature flags:
- [ ] Changes UI
- [ ] Includes DB Migration (follow approval process in [SIP-59](https://github.com/apache/superset/issues/13351))
- [ ] Migration is atomic, supports rollback & is backwards-compatible
- [ ] Confirm DB migration upgrade and downgrade tested
- [ ] Runtime estimates and downtime expectations provided
- [ ] Introduces new feature or API
- [ ] Removes existing feature or API
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [PR] fix(scatter): Fix ad-hoc metric for pointsize [superset]
Posted by "codeant-ai-for-open-source[bot] (via GitHub)" <gi...@apache.org>.
codeant-ai-for-open-source[bot] commented on PR #37669:
URL: https://github.com/apache/superset/pull/37669#issuecomment-3853520731
## **Sequence Diagram**
The PR fixes handling of metric-based point sizes by preserving full adhoc metric objects (including expressionType/sqlExpression) when building the query, deduplicating by metric label, and using only the label string for orderby. This prevents the backend "Metric does not exist" errors for custom SQL metrics.
```mermaid
sequenceDiagram
participant UI
participant buildQuery
participant QueryContext
UI->>buildQuery: Submit formData with point_radius_fixed (type: metric, value: adhoc SQL object)
buildQuery->>buildQuery: Detect metric type; preserve full QueryFormMetric object (don't extract label)
buildQuery->>buildQuery: Deduplicate metrics by getMetricLabel and add metric object to metrics array
buildQuery->>QueryContext: Return query with metrics containing adhoc metric OBJECT and orderby using getMetricLabel(metric) string
QueryContext-->>UI: Query ready for backend (adhoc metric preserved, orderby uses label)
```
---
*Generated by [CodeAnt AI](https://codeant.ai)*
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [PR] fix(scatter): Fix ad-hoc metric for pointsize [superset]
Posted by "bito-code-review[bot] (via GitHub)" <gi...@apache.org>.
bito-code-review[bot] commented on PR #37669:
URL: https://github.com/apache/superset/pull/37669#issuecomment-3853280905
AI Code Review is in progress (usually takes 3 to 15 minutes unless it's a very large PR).
<details>
<summary>
Bito Usage Guide
</summary>
**Commands**
Type the following command in the pull request comment and save the comment.
- `/review` - Manually triggers a full AI review.
- `/pause` - Pauses automatic reviews on this pull request.
- `/resume` - Resumes automatic reviews.
- `/resolve` - Marks all Bito-posted review comments as resolved.
- `/abort` - Cancels all in-progress reviews.
Refer to the <a href="https://docs.bito.ai/bito-dev-agents/ai-code-review-agent/available-commands" target="_blank" rel="noopener noreferrer">documentation</a> for additional commands.
**Configuration**
This repository uses `Superset` You can customize the agent settings <a href="https://alpha.bito.ai/home/ai-agents/code-review-agent" target="_blank" rel="noopener noreferrer">here</a> or contact your Bito workspace admin at evan@preset.io.
**Documentation & Help**
- <a href="https://docs.bito.ai/bito-dev-agents/ai-code-review-agent/getting-started/install-run-using-bito-cloud/create-or-customize-an-agent-instance" target="_blank" rel="noopener noreferrer">Customize agent settings</a>
- <a href="https://docs.bito.ai/bito-dev-agents/ai-code-review-agent/implementing-custom-code-review-rules" target="_blank" rel="noopener noreferrer">Review rules</a>
- <a href="https://docs.bito.ai/bito-dev-agents/ai-code-review-agent" target="_blank" rel="noopener noreferrer">General documentation</a>
- <a href="https://docs.bito.ai/bito-dev-agents/ai-code-review-agent/faqs" target="_blank" rel="noopener noreferrer">FAQ</a>
</details>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [PR] fix(scatter): Fix ad-hoc metric for pointsize [superset]
Posted by "netlify[bot] (via GitHub)" <gi...@apache.org>.
netlify[bot] commented on PR #37669:
URL: https://github.com/apache/superset/pull/37669#issuecomment-3853551795
### <span aria-hidden="true">✅</span> Deploy Preview for *superset-docs-preview* ready!
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 2b2ace1b6e7c69f1c11f24c20bfd414246c45699 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/projects/superset-docs-preview/deploys/6984951c9a1b1c0008522e87 |
|<span aria-hidden="true">😎</span> Deploy Preview | [https://deploy-preview-37669--superset-docs-preview.netlify.app](https://deploy-preview-37669--superset-docs-preview.netlify.app) |
|<span aria-hidden="true">📱</span> Preview on mobile | <details><summary> Toggle QR Code... </summary><br /><br /><br /><br />_Use your smartphone camera to open QR code link._</details> |
---
<!-- [superset-docs-preview Preview](https://deploy-preview-37669--superset-docs-preview.netlify.app) -->
_To edit notification comments on pull requests, go to your [Netlify project configuration](https://app.netlify.com/projects/superset-docs-preview/configuration/notifications#deploy-notifications)._
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [PR] fix(scatter): Fix ad-hoc metric for pointsize [superset]
Posted by "msyavuz (via GitHub)" <gi...@apache.org>.
msyavuz commented on code in PR #37669:
URL: https://github.com/apache/superset/pull/37669#discussion_r2773261560
##########
superset-frontend/plugins/legacy-preset-chart-deckgl/src/layers/Scatter/buildQuery.ts:
##########
@@ -82,26 +86,41 @@ export default function buildQuery(formData: DeckScatterFormData) {
// Only add metric if point_radius_fixed is a metric type
const isMetric = isMetricValue(point_radius_fixed);
- const metricValue = isMetric
- ? extractMetricKey(point_radius_fixed?.value)
- : null;
+ // Extract metric value, handling both legacy string format and object format
+ let metricValue: QueryFormMetric | null = null;
+ if (isMetric) {
+ if (typeof point_radius_fixed === 'string') {
+ // Legacy string format: treat the string itself as the metric
+ metricValue = point_radius_fixed;
+ } else if (
+ point_radius_fixed?.value !== undefined &&
+ typeof point_radius_fixed.value !== 'number'
+ ) {
+ // Metric object format: use the metric value (string or adhoc metric object)
+ metricValue = point_radius_fixed.value as QueryFormMetric;
+ }
+ }
// Preserve existing metrics and only add radius metric if it's metric-based
const existingMetrics = baseQueryObject.metrics || [];
- const radiusMetrics = processMetricsArray(
- metricValue ? [metricValue] : [],
+ // Deduplicate metrics using getMetricLabel for comparison
+ const existingLabels = new Set(
+ existingMetrics.map(m => getMetricLabel(m)),
);
- // Deduplicate metrics to avoid adding the same metric twice
- const metricsSet = new Set([...existingMetrics, ...radiusMetrics]);
- const metrics = Array.from(metricsSet);
+ const metrics: QueryFormMetric[] =
+ metricValue && !existingLabels.has(getMetricLabel(metricValue))
+ ? [...existingMetrics, metricValue]
+ : [...existingMetrics];
Review Comment:
```suggestion
: existingMetrics;
```
##########
superset-frontend/plugins/legacy-preset-chart-deckgl/src/layers/Scatter/buildQuery.ts:
##########
@@ -82,26 +86,41 @@ export default function buildQuery(formData: DeckScatterFormData) {
// Only add metric if point_radius_fixed is a metric type
const isMetric = isMetricValue(point_radius_fixed);
- const metricValue = isMetric
- ? extractMetricKey(point_radius_fixed?.value)
- : null;
+ // Extract metric value, handling both legacy string format and object format
+ let metricValue: QueryFormMetric | null = null;
+ if (isMetric) {
+ if (typeof point_radius_fixed === 'string') {
+ // Legacy string format: treat the string itself as the metric
+ metricValue = point_radius_fixed;
+ } else if (
+ point_radius_fixed?.value !== undefined &&
+ typeof point_radius_fixed.value !== 'number'
+ ) {
+ // Metric object format: use the metric value (string or adhoc metric object)
+ metricValue = point_radius_fixed.value as QueryFormMetric;
+ }
+ }
Review Comment:
Maybe we can flatten this a bit more? It's just a nit though
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [PR] fix(scatter): Fix ad-hoc metric for pointsize [superset]
Posted by "bito-code-review[bot] (via GitHub)" <gi...@apache.org>.
bito-code-review[bot] commented on PR #37669:
URL: https://github.com/apache/superset/pull/37669#issuecomment-3860349202
AI Code Review is in progress (usually takes 3 to 15 minutes unless it's a very large PR).
<details>
<summary>
Bito Usage Guide
</summary>
**Commands**
Type the following command in the pull request comment and save the comment.
- `/review` - Manually triggers a full AI review.
- `/pause` - Pauses automatic reviews on this pull request.
- `/resume` - Resumes automatic reviews.
- `/resolve` - Marks all Bito-posted review comments as resolved.
- `/abort` - Cancels all in-progress reviews.
Refer to the <a href="https://docs.bito.ai/bito-dev-agents/ai-code-review-agent/available-commands" target="_blank" rel="noopener noreferrer">documentation</a> for additional commands.
**Configuration**
This repository uses `Superset` You can customize the agent settings <a href="https://alpha.bito.ai/home/ai-agents/code-review-agent" target="_blank" rel="noopener noreferrer">here</a> or contact your Bito workspace admin at evan@preset.io.
**Documentation & Help**
- <a href="https://docs.bito.ai/bito-dev-agents/ai-code-review-agent/getting-started/install-run-using-bito-cloud/create-or-customize-an-agent-instance" target="_blank" rel="noopener noreferrer">Customize agent settings</a>
- <a href="https://docs.bito.ai/bito-dev-agents/ai-code-review-agent/implementing-custom-code-review-rules" target="_blank" rel="noopener noreferrer">Review rules</a>
- <a href="https://docs.bito.ai/bito-dev-agents/ai-code-review-agent" target="_blank" rel="noopener noreferrer">General documentation</a>
- <a href="https://docs.bito.ai/bito-dev-agents/ai-code-review-agent/faqs" target="_blank" rel="noopener noreferrer">FAQ</a>
</details>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [PR] fix(scatter): Fix ad-hoc metric for pointsize [superset]
Posted by "bito-code-review[bot] (via GitHub)" <gi...@apache.org>.
bito-code-review[bot] commented on PR #37669:
URL: https://github.com/apache/superset/pull/37669#issuecomment-3847438383
AI Code Review is in progress (usually takes 3 to 15 minutes unless it's a very large PR).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [PR] fix(scatter): Fix ad-hoc metric for pointsize [superset]
Posted by "codeant-ai-for-open-source[bot] (via GitHub)" <gi...@apache.org>.
codeant-ai-for-open-source[bot] commented on code in PR #37669:
URL: https://github.com/apache/superset/pull/37669#discussion_r2769070836
##########
superset-frontend/plugins/legacy-preset-chart-deckgl/src/layers/Scatter/buildQuery.ts:
##########
@@ -82,26 +83,32 @@ export default function buildQuery(formData: DeckScatterFormData) {
// Only add metric if point_radius_fixed is a metric type
const isMetric = isMetricValue(point_radius_fixed);
- const metricValue = isMetric
- ? extractMetricKey(point_radius_fixed?.value)
- : null;
+ // When type is 'metric', value is QueryFormMetric (string or adhoc object)
+ const metricValue: QueryFormMetric | null =
+ isMetric && point_radius_fixed?.value !== undefined
+ ? (point_radius_fixed.value as QueryFormMetric)
+ : null;
Review Comment:
**Suggestion:** The new logic only reads `point_radius_fixed.value` when it is an object, so if `point_radius_fixed` is provided in the legacy string form (which `isMetricValue` and `getMetricLabelFromFormData` still support elsewhere), `isMetric` becomes true but `metricValue` stays null and the radius metric is never added to `metrics` or `orderby`. This breaks existing charts saved with a string radius metric: the backend never computes the radius metric column while `transformProps` still expects it, resulting in missing radius values and inconsistent behavior. Update `metricValue` derivation to also handle the case where `point_radius_fixed` itself is a string, and to avoid treating numeric fixed values as metrics. [logic error]
<details>
<summary><b>Severity Level:</b> Major ⚠️</summary>
```mdx
- ❌ Scatter point radius metric missing in saved legacy charts.
- ⚠️ Visualization shows missing or default point sizes.
- ⚠️ Backend doesn't compute required radius column.
- ⚠️ Affects charts saved before metric-object migration.
- ⚠️ Suggestion fixes real compatibility regression.
```
</details>
```suggestion
let metricValue: QueryFormMetric | null = null;
if (isMetric) {
if (typeof point_radius_fixed === 'string') {
// Legacy string format: treat the string itself as the metric
metricValue = point_radius_fixed;
} else if (
point_radius_fixed?.value !== undefined &&
typeof point_radius_fixed.value !== 'number'
) {
// Metric object format: use the metric value (string or adhoc metric object)
metricValue = point_radius_fixed.value as QueryFormMetric;
}
}
```
<details>
<summary><b>Steps of Reproduction ✅ </b></summary>
```mdx
1. Open a saved Scatter chart that was created before the new PR fix and that uses the
legacy string form for the radius metric (point_radius_fixed stored as a plain string).
The UI stores this value in the chart form data used by buildQuery (file:
superset-frontend/plugins/legacy-preset-chart-deckgl/src/layers/Scatter/buildQuery.ts).
2. The chart rendering path calls buildQuery(formData) (function defined at top of the
same file). At runtime buildQuery reaches the snippet beginning at line 84: it calls
isMetricValue(point_radius_fixed) (line 84) which returns true for legacy string metrics.
3. Immediately after, the current code computes metricValue using the conditional
expression at lines 86-90. Because the legacy value is a string and not an object with a
.value property, point_radius_fixed?.value is undefined, so metricValue becomes null
(lines 86-90).
4. Later in the same function (lines 92-101 in the final file), metricValue being null
causes the radius metric not to be appended to the metrics array and not to be added to
orderby (metrics stays as existingMetrics, and orderby falls back to
baseQueryObject.orderby). Therefore the query sent to the backend does not request the
radius metric column.
5. The backend therefore does not compute the metric column for point radius. The
front-end code that expects the radius column (the deck.gl layer transform/transformProps
logic described in the PR summary) receives missing radius values, resulting in
empty/missing point sizes or errors in the visualization.
6. Expected correct behavior per PR description: legacy string metrics should be treated
as valid metrics and included in metrics/orderby. The improved_code change sets
metricValue when point_radius_fixed is a string, restoring the missing metric column in
the query and preventing missing radius values.
7. Note: this reproduction is based on the actual lines in buildQuery.ts (lines 84-101)
where isMetric is computed and metricValue is derived, and on the later use of
metrics/orderby in the same function (lines 92-112) which control query composition.
```
</details>
<details>
<summary><b>Prompt for AI Agent 🤖 </b></summary>
```mdx
This is a comment left during a code review.
**Path:** superset-frontend/plugins/legacy-preset-chart-deckgl/src/layers/Scatter/buildQuery.ts
**Line:** 87:90
**Comment:**
*Logic Error: The new logic only reads `point_radius_fixed.value` when it is an object, so if `point_radius_fixed` is provided in the legacy string form (which `isMetricValue` and `getMetricLabelFromFormData` still support elsewhere), `isMetric` becomes true but `metricValue` stays null and the radius metric is never added to `metrics` or `orderby`. This breaks existing charts saved with a string radius metric: the backend never computes the radius metric column while `transformProps` still expects it, resulting in missing radius values and inconsistent behavior. Update `metricValue` derivation to also handle the case where `point_radius_fixed` itself is a string, and to avoid treating numeric fixed values as metrics.
Validate the correctness of the flagged issue. If correct, How can I resolve this? If you propose a fix, implement it and please make it concise.
```
</details>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [PR] fix(scatter): Fix ad-hoc metric for pointsize [superset]
Posted by "msyavuz (via GitHub)" <gi...@apache.org>.
msyavuz commented on PR #37669:
URL: https://github.com/apache/superset/pull/37669#issuecomment-3852320478
Thanks a lot for fixing this!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [PR] fix(scatter): Fix ad-hoc metric for pointsize [superset]
Posted by "alexandrusoare (via GitHub)" <gi...@apache.org>.
alexandrusoare merged PR #37669:
URL: https://github.com/apache/superset/pull/37669
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [PR] fix(scatter): Fix ad-hoc metric for pointsize [superset]
Posted by "msyavuz (via GitHub)" <gi...@apache.org>.
msyavuz commented on PR #37669:
URL: https://github.com/apache/superset/pull/37669#issuecomment-3852223445
Can we link the pr that introduced this issue for future reference?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [PR] fix(scatter): Fix ad-hoc metric for pointsize [superset]
Posted by "bito-code-review[bot] (via GitHub)" <gi...@apache.org>.
bito-code-review[bot] commented on PR #37669:
URL: https://github.com/apache/superset/pull/37669#issuecomment-3853937012
AI Code Review is in progress (usually takes 3 to 15 minutes unless it's a very large PR).
<details>
<summary>
Bito Usage Guide
</summary>
**Commands**
Type the following command in the pull request comment and save the comment.
- `/review` - Manually triggers a full AI review.
- `/pause` - Pauses automatic reviews on this pull request.
- `/resume` - Resumes automatic reviews.
- `/resolve` - Marks all Bito-posted review comments as resolved.
- `/abort` - Cancels all in-progress reviews.
Refer to the <a href="https://docs.bito.ai/bito-dev-agents/ai-code-review-agent/available-commands" target="_blank" rel="noopener noreferrer">documentation</a> for additional commands.
**Configuration**
This repository uses `Superset` You can customize the agent settings <a href="https://alpha.bito.ai/home/ai-agents/code-review-agent" target="_blank" rel="noopener noreferrer">here</a> or contact your Bito workspace admin at evan@preset.io.
**Documentation & Help**
- <a href="https://docs.bito.ai/bito-dev-agents/ai-code-review-agent/getting-started/install-run-using-bito-cloud/create-or-customize-an-agent-instance" target="_blank" rel="noopener noreferrer">Customize agent settings</a>
- <a href="https://docs.bito.ai/bito-dev-agents/ai-code-review-agent/implementing-custom-code-review-rules" target="_blank" rel="noopener noreferrer">Review rules</a>
- <a href="https://docs.bito.ai/bito-dev-agents/ai-code-review-agent" target="_blank" rel="noopener noreferrer">General documentation</a>
- <a href="https://docs.bito.ai/bito-dev-agents/ai-code-review-agent/faqs" target="_blank" rel="noopener noreferrer">FAQ</a>
</details>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org