-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Add Target column to the LinkFieldIndex table #16380
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I only briefly checked out the code, but I'll be able to properly test and asses it once I'm back from holiday, next Tuesday.
src/OrchardCore.Modules/OrchardCore.ContentFields/Indexing/SQL/Migrations.cs
Show resolved
Hide resolved
src/OrchardCore.Modules/OrchardCore.ContentFields/Indexing/SQL/LinkFieldIndexProvider.cs
Show resolved
Hide resolved
So nobody agrees with my comments ? (#16326 (comment)) we just accept anything in the index? (or graphql, sql index, ... why stop there). Even when there is an obvious alternative: adding fields using existing types. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The code is OK now, but yeah, perhaps we should not have this in the index, in the first place.
closing this in favor of #16397 |
Fix #16378