From 7c174a01c746081d61c02e20649b66099bfa34a8 Mon Sep 17 00:00:00 2001 From: Robin Malfait Date: Thu, 29 Sep 2022 17:12:09 +0200 Subject: [PATCH] annotate any-type test with a bit more information Just for future debugging reasons! --- tests/any-type.test.js | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/tests/any-type.test.js b/tests/any-type.test.js index f0ec127f839b..c7ffa8e03643 100644 --- a/tests/any-type.test.js +++ b/tests/any-type.test.js @@ -1,5 +1,20 @@ import { run, html, css } from './util/run' +// Hi there, so you are debugging this test because something failed... right? Well we can look into +// the future and guessed that this would happen. So basically it means that we (it was probably +// you, silly) introduced a new plugin that conflicts with an existing plugin that has (either +// implicit or explicit) an `any` type. +// +// Now it is your job to decide which one should win, and mark that one with +// ```diff +// - 'any' +// + ['any', { preferOnConflict: true }] +// ``` +// in the corePlugins.js file. +// +// You probably want to let the original one win for backwards compatible reasons. +// +// Good luck! test('any types are set on correct plugins', () => { let config = { content: [