Hi!
This is mostly a warning for Quark developers, but also for users:
- If a Quark overwrites a method, it does so globally - so you might start seeing unexpected behaviour in normal usage. This is particularly dangerous for core classes, hence the warning. Ultimately, Quarks shouldn’t do this, however they may not do it on purpose, see below
- If a Quark extends a core class, this is usually fine. But if the core class gets updated and adds a method of the same name, then there’s a big problem - so again, the warning is valid, letting you know the method might not behave as you expect.
Hopefully that’s helpful.
Best,
James