Tensegritics / Tensegritics/ClojureDart
Do not leave flutter on cljd compiler error
Nobody has claimed this yet.
- Dominant language
- Clojure
- Stars
- 1.6k
- Forks
- 119
- PR merge metrics
- No merged PRs in 30d
Description
The compiler fails when one of the cljd files is not readable during cljd compilation. This can happen because I compulsively save one by doing several small updates in a row, or when I do some changes over several files and save them one after the other.
When it happens, it leaves the flutter env so I lose the current app state and I have to start over the clj -Mcljd flutter command.
Example :
Execution error (FileNotFoundException) at java.io.FileInputStream/open0 (FileInputStream.java:-2).
src/kazoo/widgets.cljd (Aucun fichier ou dossier de ce type)
Would it be feasable to have some kind of retry to avoid this, as in this case the file will only be unavailable for a short time ? Or to catch the error so we don't have to start all over, but only to trigger a new compile ?
Contributor guide
No contributing guide indexed for this repository
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 running clj -Mcljd flutter and trace how cljd handles the reported FileNotFoundException when a .cljd file is temporarily unreadable. The issue is done when a short-lived missing-file error can retry or trigger compilation again without leaving the Flutter environment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure, dart, flutter
- Domain
- build-system, compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100