nextcloud / nextcloud/android-library
`CreationException` is marked as `@Deprecated`.
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 105
- Forks
- 99
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 21
Description
CreationException is marked as @Deprecated.
I think it's rather kludgy to fail with exceptions in general. Many developers don't even know how to handle exceptions or care about handling them, using try-catch block to suppress them (sic!):
try {
veryImportantThng = makeStuff();
} catch(VeryNastyException ex) {
log(ex);
}
continue and probably crash later
Maybe we can return a client that fast-fails the operation? This way we can remove a lot of checks in the client code and make it safer:
- no edge cases
- no null handling
Originally posted by @ezaquarii in https://github.com/nextcloud/android/pull/4900
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating CreationException and the client API that currently exposes it; the issue names no files or tests. Review the linked pull request context and determine whether a fast-failing client can replace exception-based handling, with the API behavior and migration scope agreed before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100