This repository has been archived by the owner on Dec 27, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 548
dat API: writeFile encoding option is not optional #237
Comments
You're assumption is right, it should be optional. What exception did you get? |
A WriteFileError, I think. The error message was an empty string. |
Can you confirm that was the error? A WriteFileError is an unexpected internal issue. If you run Beaker from the CLI, you should see a more descriptive error in the console if that occurs. |
Also what was your usage of the method? |
Ah, the CLI log was helpful. I had a trailing slash in the filename... My bad, sorry for the noise :) |
No worries!
…On Sat, Dec 31, 2016 at 1:03 PM, Marcel Klehr ***@***.***> wrote:
Ah, the I log was helpful. I had a trailing slash in the filename... My
bad, sorry for the noise :)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#237 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABNhU8AXwrvtGagRzxEyPjcqssuYwZy7ks5rNqcagaJpZM4LYmFw>
.
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Operation System: Ubuntu 16.04
Beaker Version: 8c32d5c
I tried to dat.writeFile without specifying an encoding and got an exception. I assumed utf8 (or anything else, really) would be the default encoding due to the
?
in the method signature in the docs. I might have been assuming wrong, though :)The text was updated successfully, but these errors were encountered: