The key "ResourceModules" in extension.schema.v1.json and extension.schema.v2.json should be marked as deprecated since T109837 / I6c21e3e47c23df33a04c42ce94bd4c1964599c7f
Due to use of "additionalProperties": false it must stay for valid extension.json.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T192155 Allow deprecation of keys in extension.schema for core and extensions | |||
| Declined | None | T186363 Set position top|bottom for ResourceLoader config to deprecated in extension.schema |
I have no idea if there is a deprecation way for keys in the extension.schema or if that is needed
When running validateRegistrationFile.php it could shown to the developer that some keys are no longer needed or should replaced. But I have no idea if that is a good way to think about or discussion further. Feel free to hijack the idea.
I think this would be better if ResourceLoader itself emitted a deprecation warning for these...
The position attribute was an optimisation. It did not change functional behaviour. As such, I do not plan to apply any form of deprecation or mandatory migration.
In fact, the feature has been removed already several years ago. Starting deprecation now seems odd, and is imho not a good use of developers time to write, review, release, act on in maintained code, and eventually (when?) to remove the detection again.
If anyone feels particularly strongly about these ignored additional keys, they are free to remove them from code they maintain at their earliest convenience. However, as currently written I'm declining this feature request for ResourceLoader and the code we maintain for it in the ExtensionRegistry.
I suppose it wouldn't be a formal deprecation in the normal sense, the main thing we want to do is emit warnings for when position top/bottom are still configured since they're useless, and at worst confusing if people think they're still being respected. Do you think that adding warnings isn't worth it?
If anyone feels particularly strongly about these ignored additional keys, they are free to remove them from code they maintain at their earliest convenience. However, as currently written I'm declining this feature request for ResourceLoader and the code we maintain for it in the ExtensionRegistry.
Ack. I'll work on that as well then.