Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Changes required due to TextBuffer.save becoming async in Atom 1.19 #1273

Closed
maxbrunsfeld opened this issue Jun 14, 2017 · 4 comments
Closed
Labels

Comments

@maxbrunsfeld
Copy link

Hi! Thanks for maintaining the atom-typescript package!

In Atom v1.19, we will release a major change to Atom's core text buffer data structure. As part of this change, we have made TextBuffer.save asynchronous; rather than blocking until the save is complete, it now immediately returns a Promise that resolves when the save is complete. Because of this, a few other Atom APIs that use save have similarly become async:

  • Pane.close
  • TextBuffer.save
  • TextEditor.save
  • Pane.saveItem
  • Pane.saveItemAs
  • Pane.saveActiveItem
  • Pane.saveActiveItemAs
  • Pane.saveItems
  • Workspace.saveActivePaneItem
  • Workspace.saveActivePaneItemAs

Effects on this package

We think this package could be impacted by this upgrade because it calls the changed methods in the following places:

We found these calls using a regex search, so this list might be incomplete, and it might contain some false positives.

What to do about the change

It should be pretty easy to adjust your package code and/or tests to work with the new async behavior, and to simultaneously keep it working with older versions of Atom. Here are some examples of pull requests we opened on our bundled packages to cope with the change:

@pablomayobre
Copy link

Luckily this package doesn't seem affected by this issue, since it doesn't rely on TextBuffer.save being synchronous and instead waits for TextBuffer.onDidSave

@opavader
Copy link

@positive07 have you tried it with it beta1, atleast the autocomplete on type is not working.

@pablomayobre
Copy link

I don't see any link between autocomplete and this issue.

If this issue were to affect anything it would be the rename-refactor command

@github-actions
Copy link

This issue has been marked as stale because it did not have any activity for the last 90 days or more. Remove the stale label or comment or this will be closed in 14 days

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants