Skip to content

typo #2800

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Jul 5, 2017
Merged

typo #2800

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/2.0-breaking-changes/nest-breaking-changes.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,7 +67,7 @@ Each individual moving part is further explained in the index.html[documentation
[float]
=== Inferred types

Many places that only took a string now take a more strongly typed object, <`Id`,ids-inference>>, <<field-inference,`Field`>>, <<field-inference,`Fields`>>, <<index-name-inference,`Index`>>, <<indices-paths,`Indices`>>, `Type`, `Types`, <<document-paths,`DocumentPath<T>`>>. It's good to know that in most cases you can still implicitly convert to them from `string`, `long`, `Guid` where it makes sense.
Many places that only took a string now take a more strongly typed object, <<`Id`,ids-inference>>, <<field-inference,`Field`>>, <<field-inference,`Fields`>>, <<index-name-inference,`Index`>>, <<indices-paths,`Indices`>>, `Type`, `Types`, <<document-paths,`DocumentPath<T>`>>. It's good to know that in most cases you can still implicitly convert to them from `string`, `long`, `Guid` where it makes sense.

If you are using `C# 6` you can also staticly import `using static Nest.Infer`. This will allow you to write

Expand Down