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

Rename TypeScript interfaces not to conflict with named values #266

Merged
merged 1 commit into from
Jul 26, 2018

Conversation

Avaq
Copy link
Member

@Avaq Avaq commented Jul 26, 2018

Fixes #259

@Avaq Avaq added the breaking label Jul 26, 2018
@@ -342,16 +342,16 @@ declare module 'fluture' {

}

export var Future: Fluture
export var Future: FutureTypeRep
export default Future
Copy link
Member Author

@Avaq Avaq Jul 26, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's all about this line here (346). This used to mean "export the Future interface as default", and now it means "export the Future value as default".

@codecov-io
Copy link

Codecov Report

Merging #266 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@          Coverage Diff          @@
##           master   #266   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files          49     49           
  Lines        1211   1211           
=====================================
  Hits         1211   1211

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c5c84d6...83734cc. Read the comment docs.

@Avaq Avaq merged commit 69f9492 into master Jul 26, 2018
@Avaq Avaq deleted the avaq/rename-interfaces branch July 26, 2018 10:08
Avaq added a commit that referenced this pull request Jul 26, 2018
Breaking changes

- #224 Exceptions are now caught and rethrown in `fork`.
- #230 Many of the TypeScript type definitions that used `never` now use a
  generic instead.
- #238 When unsubscribing from a Future created by `hook`, the cancellation
  signal is no longer sent to the disposal Future.
- #266 Exported TypeScript interfaces have been renamed to avoid naming
  conflicts with exported values.

New features

- #250 Included interoperability with Sanctuary Show
- #261 Added a new function, `forkCatch`, which allows for exception recovery.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants