Fix TypeScript exports for classes #428
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
They were previously exported in a way that did not allow user code to create instances using `new`. For example: ```typescript const date = new neo4j.types.Date(1, 2, 3); ``` did not compile. Added tests for all types exported from `neo4j.types` object.
ali-ince
reviewed
Nov 16, 2018
Node, Relationship, UnboundRelationship, PathSegment, Path and Record should not be exposed in `neo4j.types` constant.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
They were previously exported in a way that did not allow user code to create instances using
new. For example:did not compile.
Added tests for all types exported from
neo4j.typesobject.Fixes #426