From 62e9598c1f2b21bfcbd01c8954c0e0d274c50b5b Mon Sep 17 00:00:00 2001 From: Jason Stoltzfus Date: Wed, 3 Feb 2021 07:28:47 -0500 Subject: [PATCH] Updated comment --- .../relevance_tuning/relevance_tuning_logic.test.ts | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/x-pack/plugins/enterprise_search/public/applications/app_search/components/relevance_tuning/relevance_tuning_logic.test.ts b/x-pack/plugins/enterprise_search/public/applications/app_search/components/relevance_tuning/relevance_tuning_logic.test.ts index 903532285a8c9..03576ec2b8d72 100644 --- a/x-pack/plugins/enterprise_search/public/applications/app_search/components/relevance_tuning/relevance_tuning_logic.test.ts +++ b/x-pack/plugins/enterprise_search/public/applications/app_search/components/relevance_tuning/relevance_tuning_logic.test.ts @@ -191,9 +191,9 @@ describe('RelevanceTuningLogic', () => { describe('selectors', () => { describe('engineHasSchemaFields', () => { - it('should false if there is only a single field in a schema', () => { - // I believe this is because schemas *always* have an ID, and we don't consider that - // a tunable field + it('should return false if there is only a single field in a schema', () => { + // This is because if a schema only has a single field, it is "id", which we do not + // consider a tunable field. mount({ schema: { id: 'foo',