Remap encrypted paths in exception messsages

Open
#12 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
java

Research direction

Start by locating the delegate filesystem exception-handling paths and examining how encrypted and decrypted paths are represented. Confirm which exceptions can be remapped and define done as showing corresponding decrypted paths whenever a mapping is possible, while preserving useful messages when it is not.

Written by the indexing model from the issue text.

Description

Whenever the delegate filesystem throws exceptions those may contain encrypted paths. We should map them to the corresponding decrypted paths whenever possible, to make those exceptions more useful to the users.

Dominant language
Java
Stars
110
Forks
39
Avg merge
1d 28m
Merged PRs (30d)
4

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cryptomator/cryptofs

All issues in cryptomator/cryptofs

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.