Skip to content

fix(providers): the company is called Drime, not Drime Cloud (#347) - #520

Merged
axpnet merged 1 commit into
mainfrom
fix/drime-naming-347
Jul 30, 2026
Merged

fix(providers): the company is called Drime, not Drime Cloud (#347)#520
axpnet merged 1 commit into
mainfrom
fix/drime-naming-347

Conversation

@axpnet

@axpnet axpnet commented Jul 30, 2026

Copy link
Copy Markdown
Member

Split out of #519 so both changes fit under CodeRabbit's 100-file review limit: this one is a rename, 47 of its files are locale JSONs, and it reads better on its own anyway.

@EhudKirsh read the tracker note where I had recorded "Drime Cloud" as a name AeroFTP was getting wrong in reverse, and told me the reverse was the mistake:

I think it's just 'Drime' actually. It's not really a suite of sibling tools like with pCloud, MEGA and others [...] Also, "Drime Cloud" isn't written anywhere on its home page https://drime.cloud.

He is right. Their title tag reads "Drime | Secure File Collaboration & Cloud Storage Solutions", the page says "Drime is easy to use, secure, and built for everyone", and "Drime Cloud" appears only inside the app.drime.cloud URL.

The catalogue had it inside out — company: 'Drime Cloud', parentCompany: 'Drime' — as though the cloud drive were a product under a parent company, the way pCloud Drive sits under pCloud. There is no parent here, so the entry is now simply company: 'Drime', and README, docs/PROVIDERS.md and cli_catalog.json are regenerated from it (gen:providers-table, gen:cli-catalog) rather than hand-edited, so the tables that the drift guard test compares cannot fall out of step.

Renamed where a person reads it: eleven strings across the GUI, 48 across all 47 locale files, and seven user-facing strings in the Rust provider — its display name, its connection and rate-limit errors, and its quota line.

Deliberately unchanged, since nobody sees them: the drime protocol id, the DrimeCloud enum variant, drime_cloud.rs and the comments inside it. Also unchanged is SECURITY-EVIDENCE-v2.6.4.md, which is a dated record of what was true at the time.

Verification

tsc clean, npm run build ok, vitest 545/545 (the README/PROVIDERS drift guards pass against the regenerated tables), cargo check --all-features clean, cargo fmt --check clean, i18n:validate 46/46 with 0 missing keys and 0 placeholders.

Reported by @EhudKirsh in discussion #347.

Not marked as closing anything: the thread stays open for the reporter to confirm.

Summary by CodeRabbit

  • Documentation

    • Updated provider documentation and capability tables to consistently use the name Drime.
  • User Interface

    • Updated provider names, connection messages, saved server details, discovery listings, and catalog entries to display Drime.
  • Localization

    • Updated Drime descriptions and tooltips across supported languages while preserving storage and REST API details.
  • Error Messages

    • Updated connection and authentication messages to reference Drime consistently.

Ehud read the tracker note where I recorded "Drime Cloud" as a name AeroFTP
was getting wrong in reverse, and said the reverse was the mistake: it is just
Drime. He is right, and their own site says so — the title tag reads "Drime |
Secure File Collaboration & Cloud Storage Solutions", the page says "Drime is
easy to use, secure, and built for everyone", and "Drime Cloud" appears only
inside the app.drime.cloud URL.

The catalogue had it inside out: `company: 'Drime Cloud', parentCompany:
'Drime'`, as though the cloud drive were a product under a parent company, the
way pCloud Drive sits under pCloud. There is no parent here, so the entry is
now simply Drime, and README, docs/PROVIDERS.md and cli_catalog.json are
regenerated from it rather than edited.

Renamed where a person reads it: eleven strings across the GUI, 48 across all
47 locale files, seven user-facing strings in the Rust provider (its display
name, its connection and rate-limit errors, its quota line) and the provider
tables in the docs. Deliberately unchanged: the `drime` protocol id, the
`DrimeCloud` enum variant, `drime_cloud.rs` and the comments inside it — none
of which the user ever sees — and SECURITY-EVIDENCE-v2.6.4.md, which is a
dated record of what was true then.

Reported by @EhudKirsh in discussion #347.
@snyk-io

snyk-io Bot commented Jul 30, 2026

Copy link
Copy Markdown

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@coderabbitai

coderabbitai Bot commented Jul 30, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

The PR renames the Drime provider from “Drime Cloud” to “Drime” across backend strings, frontend displays, catalogs, documentation, and all localized protocol descriptions.

Changes

Drime provider rename

Layer / File(s) Summary
Backend and catalog naming
src-tauri/src/providers/*, src-tauri/src/cli_catalog.json, src/components/providerCatalog.ts
Updates provider display names, connection messages, error text, server information, catalog company data, and provider metadata.
Frontend provider displays
src/App.tsx, src/components/*, src/components/DevTools/*
Renames Drime in protocol selection, discovery, provider dialogs, saved servers, prompts, and disclaimer handling.
Documentation and localization
README.md, docs/*, src/i18n/locales/*
Updates provider tables, integration guidance, capability references, and localized Drime descriptions.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 10.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly summarizes the main change: renaming the provider/company from Drime Cloud to Drime.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches 💡 1
📝 Generate docstrings 💡
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/drime-naming-347

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

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@README.md`:
- Line 111: Add an alt attribute with descriptive text such as “Drime” to the
image element in the Drime provider-grid entry, preserving the existing link,
source, dimensions, and label.

In `@src/i18n/locales/en.json`:
- Around line 2728-2729: Update the drimeDesc and drimeTooltip localization
strings so both use the same verified Drime storage quota, preserving their
existing descriptive and tooltip wording.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: ff53d22b-b1ae-421a-b6bd-6f962b6fe67c

📥 Commits

Reviewing files that changed from the base of the PR and between c5369ee and 52d907d.

📒 Files selected for processing (62)
  • README.md
  • docs/PROTOCOL-FEATURES.md
  • docs/PROVIDER-INTEGRATION-GUIDE.md
  • docs/PROVIDERS.md
  • src-tauri/src/cli_catalog.json
  • src-tauri/src/providers/drime_cloud.rs
  • src-tauri/src/providers/types.rs
  • src/App.tsx
  • src/components/ConnectionScreen.tsx
  • src/components/DevTools/aiChatSystemPrompt.ts
  • src/components/IntroHub/discoverData.ts
  • src/components/ProtocolSelector.tsx
  • src/components/ProvidersDialog.tsx
  • src/components/SavedServers.tsx
  • src/components/providerCatalog.ts
  • src/i18n/locales/bg.json
  • src/i18n/locales/bn.json
  • src/i18n/locales/ca.json
  • src/i18n/locales/cs.json
  • src/i18n/locales/cy.json
  • src/i18n/locales/da.json
  • src/i18n/locales/de.json
  • src/i18n/locales/el.json
  • src/i18n/locales/en.json
  • src/i18n/locales/es.json
  • src/i18n/locales/et.json
  • src/i18n/locales/eu.json
  • src/i18n/locales/fi.json
  • src/i18n/locales/fr.json
  • src/i18n/locales/gl.json
  • src/i18n/locales/hi.json
  • src/i18n/locales/hr.json
  • src/i18n/locales/hu.json
  • src/i18n/locales/hy.json
  • src/i18n/locales/id.json
  • src/i18n/locales/is.json
  • src/i18n/locales/it.json
  • src/i18n/locales/ja.json
  • src/i18n/locales/ka.json
  • src/i18n/locales/km.json
  • src/i18n/locales/ko.json
  • src/i18n/locales/lt.json
  • src/i18n/locales/lv.json
  • src/i18n/locales/mk.json
  • src/i18n/locales/ms.json
  • src/i18n/locales/nl.json
  • src/i18n/locales/no.json
  • src/i18n/locales/pl.json
  • src/i18n/locales/pt.json
  • src/i18n/locales/ro.json
  • src/i18n/locales/ru.json
  • src/i18n/locales/sk.json
  • src/i18n/locales/sl.json
  • src/i18n/locales/sr.json
  • src/i18n/locales/sv.json
  • src/i18n/locales/sw.json
  • src/i18n/locales/th.json
  • src/i18n/locales/tl.json
  • src/i18n/locales/tr.json
  • src/i18n/locales/uk.json
  • src/i18n/locales/vi.json
  • src/i18n/locales/zh.json

Comment thread README.md
Comment thread src/i18n/locales/en.json
@axpnet
axpnet merged commit 538c255 into main Jul 30, 2026
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant