Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

README.md: Correct onwriteend to onwrite #639

Merged
merged 1 commit into from
Oct 18, 2024

Conversation

GitToTheHub
Copy link
Contributor

  1. The onwriteend samples are wrong. The correct callback is onwrite for sucessful writes, as you can see here:

onwrite

// When the write has successfully completed.
this.onwrite = null;

onwriteend

// When the request has completed (either in success or failure).
this.onwriteend = null;

  1. Corrected console.log-messages in onwrite and onerror, where it mistakenly says "Successful file read..." instead of "write"

@GitToTheHub GitToTheHub force-pushed the pr-readme-correct-onwriteend branch from 4cd220c to aa6e1e9 Compare October 18, 2024 05:58
- FileWriter.onwriteend will always be called, whether the write was successful or not
- FileWrite.onwrite is the correct callback to listen on successful writes
- Correct misspelling in console.log for onwrite and onerror
@GitToTheHub GitToTheHub force-pushed the pr-readme-correct-onwriteend branch from aa6e1e9 to beed8e8 Compare October 18, 2024 06:02
@breautek breautek merged commit 1c3b28b into apache:master Oct 18, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants