Fix: steps for float precision

[ItzNotABug]

What does this PR do?

(Provide a description of what this PR does.)

Test Plan

(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work.)

Related PRs and Issues

(If this PR is related to any other PR or resolves any issue or related to any issue link all related PR and issues here.)

Have you read the Contributing Guidelines on issues?

(Write your answer here.)

Summary by CodeRabbit

• Bug Fixes
  • Updated numeric input step configuration for float and integer column values in the database console to allow flexible decimal entry without step-based restrictions.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[appwrite]

Console (appwrite/console)

Project ID: 688b7bf400350cbd60e9

Sites (1)

Site	Status	Logs	Preview	QR
console-stage 688b7cf6003b1842c9dc	Ready	View Logs	Preview URL

Tip

Git integration provides automatic deployments with optional PR comments

[coderabbitai]

Walkthrough

This pull request modifies numeric input field configurations across two Svelte components in the database management UI. The changes replace fixed step increments (0.1) with "any" step values for three input fields in float.svelte and one conditional input in integer.svelte when the column type is double. These adjustments affect the stepping behavior of numeric inputs without altering validation logic or control flow.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Pre-merge checks

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Fix: steps for float precision' directly corresponds to the main changes: modifying step attributes from 0.1 to 'any' for float/double input fields to improve precision handling.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between caa4d79 and e905188.

📒 Files selected for processing (2)

• src/routes/(console)/project-[region]-[project]/databases/database-[database]/table-[table]/columns/float.svelte
• src/routes/(console)/project-[region]-[project]/databases/database-[database]/table-[table]/rows/columns/types/integer.svelte

🧰 Additional context used

📓 Path-based instructions (5)

**/*.{ts,tsx,js,jsx,svelte}

📄 CodeRabbit inference engine (AGENTS.md)

**/*.{ts,tsx,js,jsx,svelte}: Import reusable modules from the src/lib directory using the $lib alias
Use minimal comments in code; reserve comments for TODOs or complex logic explanations
Use $lib, $routes, and $themes aliases instead of relative paths for module imports

Files:

• src/routes/(console)/project-[region]-[project]/databases/database-[database]/table-[table]/rows/columns/types/integer.svelte
• src/routes/(console)/project-[region]-[project]/databases/database-[database]/table-[table]/columns/float.svelte

src/routes/**/*.svelte

📄 CodeRabbit inference engine (AGENTS.md)

Use SvelteKit file conventions: +page.svelte for components, +page.ts for data loaders, +layout.svelte for wrappers, +error.svelte for error handling, and dynamic route params in square brackets like [param]

Files:

• src/routes/(console)/project-[region]-[project]/databases/database-[database]/table-[table]/rows/columns/types/integer.svelte
• src/routes/(console)/project-[region]-[project]/databases/database-[database]/table-[table]/columns/float.svelte

**/*.{ts,tsx,js,jsx,svelte,json}

📄 CodeRabbit inference engine (AGENTS.md)

Use 4 spaces for indentation, single quotes, 100 character line width, and no trailing commas per Prettier configuration

Files:

• src/routes/(console)/project-[region]-[project]/databases/database-[database]/table-[table]/rows/columns/types/integer.svelte
• src/routes/(console)/project-[region]-[project]/databases/database-[database]/table-[table]/columns/float.svelte

**/*.svelte

📄 CodeRabbit inference engine (AGENTS.md)

Use Svelte 5 + SvelteKit 2 syntax with TypeScript for component development

Files:

• src/routes/(console)/project-[region]-[project]/databases/database-[database]/table-[table]/rows/columns/types/integer.svelte
• src/routes/(console)/project-[region]-[project]/databases/database-[database]/table-[table]/columns/float.svelte

src/routes/**

📄 CodeRabbit inference engine (AGENTS.md)

Configure dynamic routes using SvelteKit convention with [param] syntax in route directory names

Files:

• src/routes/(console)/project-[region]-[project]/databases/database-[database]/table-[table]/rows/columns/types/integer.svelte
• src/routes/(console)/project-[region]-[project]/databases/database-[database]/table-[table]/columns/float.svelte

🧠 Learnings (3)

📓 Common learnings

Learnt from: ItzNotABug
Repo: appwrite/console PR: 2442
File: src/routes/(console)/project-[region]-[project]/databases/database-[database]/table-[table]/columns/float.svelte:88-88
Timestamp: 2025-10-04T11:46:32.504Z
Learning: In the Appwrite Console codebase, for float/double column inputs in database table column configuration files (like float.svelte), use step={0.1} for InputNumber components, not step="any". This is the established pattern for float/double precision inputs.

📚 Learning: 2025-10-04T11:46:32.504Z

Learnt from: ItzNotABug
Repo: appwrite/console PR: 2442
File: src/routes/(console)/project-[region]-[project]/databases/database-[database]/table-[table]/columns/float.svelte:88-88
Timestamp: 2025-10-04T11:46:32.504Z
Learning: In the Appwrite Console codebase, for float/double column inputs in database table column configuration files (like float.svelte), use step={0.1} for InputNumber components, not step="any". This is the established pattern for float/double precision inputs.

Applied to files:

• src/routes/(console)/project-[region]-[project]/databases/database-[database]/table-[table]/rows/columns/types/integer.svelte
• src/routes/(console)/project-[region]-[project]/databases/database-[database]/table-[table]/columns/float.svelte

📚 Learning: 2025-09-30T07:41:06.679Z

Learnt from: ItzNotABug
Repo: appwrite/console PR: 2425
File: src/routes/(console)/project-[region]-[project]/databases/database-[database]/(suggestions)/empty.svelte:454-468
Timestamp: 2025-09-30T07:41:06.679Z
Learning: In `src/routes/(console)/project-[region]-[project]/databases/database-[database]/(suggestions)/empty.svelte`, the column suggestions API (console.suggestColumns) has a maximum limit of 7 columns returned, which aligns with the initial placeholder count of 7 in customColumns.

Applied to files:

• src/routes/(console)/project-[region]-[project]/databases/database-[database]/table-[table]/rows/columns/types/integer.svelte
• src/routes/(console)/project-[region]-[project]/databases/database-[database]/table-[table]/columns/float.svelte

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: build
• GitHub Check: e2e

🔇 Additional comments (2)

src/routes/(console)/project-[region]-[project]/databases/database-[database]/table-[table]/columns/float.svelte (1)

89-89: Clarify the rationale for step="any" and whether the October pattern should be updated.

This file uses step="any" for float column inputs, which contradicts the October 2025 guidance that established step={0.1} for this exact use case. The commit message "fix: steps for precision" suggests this change was intentional, but the PR provides no explanation for reversing the previously documented pattern.

Clarify:

1. Why step="any" better handles float precision compared to step={0.1}
2. Whether the October pattern is outdated and should be updated in documentation
3. If this new pattern should be documented as the current convention for float inputs

src/routes/(console)/project-[region]-[project]/databases/database-[database]/table-[table]/rows/columns/types/integer.svelte (1)

34-34: This code change is correct and follows the established pattern.

The integer.svelte file correctly uses step="any" for double type columns, which is consistent with the pattern established in float.svelte (also created in the same commit with message "fix: steps for precision."). Both files were created together as new files and use step="any" for float/double inputs intentionally. The retrieved learning from October appears to be outdated; the current codebase pattern is definitively step="any" for float/double precision inputs.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}