Skip to content

Improve projects API and stop depending on Tauri FS types #448

Description

@cguedes

The API output for the /api/projects (list projects) and /api/projects/{id} (project details) should improve to:

  • not use full paths (the project path) bc it can be a security concern
  • use a tree output for the project filesystem instead of a flat list of filepaths
  • make sure we ignore know files (ex: .staging)
  • adopt an output type compatible (close match) to FileEntry.ts instead of the FileEntry from @tauri-apps/api/fs

After these changes we should be able to update the client code to remove convertTauriFileEntryToFileEntry

This is related to #414 and a follow-up of #425.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions