Skip to content

Rework current search scoring or implement configuration column #14

Description

@zanechua

Currently the scoring is using the 'id' of a eloquent model as it's master scoring parameter. However this will produce unintended side effects where models with e.g. a price attribute will get scored down or even filtered out.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions