Skip to content

Remove non-generic Npgsql-specific HasIndex extension method - #821

Merged
roji merged 1 commit into
npgsql:devfrom
khellang:remove-non-generic-has-index
Feb 19, 2019
Merged

Remove non-generic Npgsql-specific HasIndex extension method#821
roji merged 1 commit into
npgsql:devfrom
khellang:remove-non-generic-has-index

Conversation

@khellang

@khellangkhellang commented Feb 18, 2019

Copy link
Copy Markdown
Contributor

Re: #813. Follows EF Core's lead; dotnet/efcore#14641.

@rojiroji left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Thanks!

@khellang

Copy link
Copy Markdown
ContributorAuthor

I don't know what your routines are in terms of marking breaking changes and updating docs etc. Please let me know if there's anything more I should do.

@rojiroji added the breaking change Represents a breaking change label Feb 19, 2019
@roji

roji commented Feb 19, 2019

Copy link
Copy Markdown
Member

We don't have very good routines yet :) I've added the breaking change label as a start. Ideally PRs should contain a note in doc/release-notes about the breaking change (and even just general documentation for the feature implemented), but I think in this case it's not really needed as the breaking change is following a general EF Core breaking change. We can always one later if we feel it's necessary.

@roji
roji merged commit e94d4a7 into npgsql:devFeb 19, 2019
@khellang
khellang deleted the remove-non-generic-has-index branch February 19, 2019 12:53
@KexyBiscuitKexyBiscuit mentioned this pull request Feb 20, 2019
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

breaking changeRepresents a breaking change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@khellang@roji@YohDeadfall@austindrenski