fix: dynamo db ui query issues fix

[Blankll]

fix: dynamo db ui query issues fix

• set index name to null when the user selects the main table
• fix scrollbar issue in UI query
• fix table/index selection issue when contains index name same with table name

Refs: #142

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 52.77%. Comparing base (1ef32a9) to head (021ec1f).
Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #206   +/-   ##
=======================================
  Coverage   52.77%   52.77%           
=======================================
  Files          10       10           
  Lines         108      108           
  Branches       14       14           
=======================================
  Hits           57       57           
  Misses         49       49           
  Partials        2        2           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Copilot]

Pull Request Overview

This PR addresses several UI and query logic issues in the DynamoDB editor, including handling the main-table vs. index selection, fixing scrollbars for long forms and results, and preventing conflicts when table and index names overlap.

• Introduce a vertical split layout with infinite scroll wrappers for query form and results
• Change form defaults and types to use null for unset keys and index
• Update selection logic to set indexName to null for the main table and improve error messaging

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File	Description
src/views/editor/dynamo-editor/components/ui-editor.vue	Restructure UI into split panels; add infinite scroll containers; update form model and query logic
src/views/editor/dynamo-editor/components/create-item.vue	Remove leftover console.log
src/datasources/dynamoApi.ts	Extend QueryParams to allow nullable index and key values
src-tauri/src/dynamo/scan_table.rs	Extract detailed error metadata and improve formatting

Comments suppressed due to low confidence (3)

src/views/editor/dynamo-editor/components/ui-editor.vue:422

• [nitpick] The class name uses “infinity” but the component is called n-infinite-scroll. Consider renaming to infinite-scroll-outer-container for consistency and clarity.

.infinity-scroll-outer-container {

src/views/editor/dynamo-editor/components/ui-editor.vue:68

• New infinite scroll containers introduce custom scrolling behavior. Consider adding a UI or integration test to verify that dynamic filter items and result rows load correctly when the content exceeds visible height.

<n-infinite-scroll style="height: 100%">

src/datasources/dynamoApi.ts:71

• Allowing partitionKey.value to be null may lead to unexpected runtime errors downstream if the API consumer expects a string. Ensure the backend or callers can handle null, or provide a default empty string instead.

value: string | null;

[Copilot]

Restoring queryResult only in the success path may leave stale data visible on errors. Consider resetting or clearing queryResult.value in the catch block (or a finally) so the UI doesn’t display old results when a query fails.

[Copilot]

[nitpick] Relying on label for matching can be brittle if labels change or collide. It’s safer to match on a unique identifier or value field to ensure the correct option is selected.

Suggested change

	selectedIndexOrTable.value = indices.find(({ label }) => label === options.label);
	selectedIndexOrTable.value = indices.find(({ key }) => key === options.key);