User talk:Jdlrobson/Stable interface policy/frontend/archive

This is great.
1000+ user scripts is a lot. This format makes me want something b/t must and should. Sj (talk) 03:32, 19 April 2023 (UTC)

Please review amendment (June 2023)
I've made some amendments based on feedback from WMF engineers.

The diff of changes here; https://www.mediawiki.org/w/index.php?title=User%3AJdlrobson%2FStable_interface_policy%2Ffrontend&diff=6010504&oldid=5935744

Summary of changes: Jdlrobson (talk) 18:17, 30 June 2023 (UTC)
 * Clarify how this links to PHP stable policy and gadget policy
 * Fix typos
 * Add additional terminology
 * Allows HTML markup to be stable if deemed necessary and why HTML markup might be important to support.
 * Details around caching updated to provide further clarity to those not familiar.
 * Attempt to define what constitutes "Gadget popularity"
 * More examples given of "stable APIs"
 * Use of Vue.js is now a MUST consideration for complex UIs.

Relax policy around deprecations
It has been suggested to relax the requirements around deprecations so that it need not apply to everything. Proposed text is: "Code that was never part of a public release, or never consumed according to codesearch MAY be changed or removed without deprecation, since it has never become part of the stable interface or used."

Proposal is to add this text to sections What to do when breaking changes to JavaScript interfaces and What_to_do_when_removing_ResourceLoader_modules

If no objections or amendments within 7 days I'll make this part of the policy. Jdlrobson (talk) 19:55, 11 July 2023 (UTC)