thiemowmde e3fdee52aa Separate names for server-side vs. client-side feature flags ... The two are different: * CiteReferencePreviews as specified in extension.json is a feature flag that allows us to disable the feature entirely. It could be named "CiteReferencePreviewsFeature" or "CiteEnableReferencePreviews", but renaming a feature flag that's already in use is hard. * The client-side flag tells the JavaScript code "you know what, it was kind of a mistake you got loaded, please stop". This is because we can not make all decisions before we register the ResourceLoader module, e.g. if the user has certain gadgets enabled. Adding the word "Active" is not a huge improvement, but at least makes the two different now. Suggestions welcome. Bug: T362771 Change-Id: I0f6a911df8772616ac50c1301f402f77dbe32089		2024-04-30 11:57:47 +00:00
..
.eslintrc.json	Move reference previews to Cite extension	2024-03-12 17:43:51 +01:00
constants.js	Move reference previews to Cite extension	2024-03-12 17:43:51 +01:00
createReferenceGateway.js	Move reference previews to Cite extension	2024-03-12 17:43:51 +01:00
createReferencePreview.js	Move reference previews to Cite extension	2024-03-12 17:43:51 +01:00
index.js	Add ReferencePreviews config checks to Cite extension	2024-04-25 12:50:27 +02:00
isReferencePreviewsEnabled.js	Separate names for server-side vs. client-side feature flags	2024-04-30 11:57:47 +00:00
OWNERS.md	Move reference previews to Cite extension	2024-03-12 17:43:51 +01:00
referencePreview.less	Move reference previews to Cite extension	2024-03-12 17:43:51 +01:00
referencePreviewsInstrumentation.js	Separate names for server-side vs. client-side feature flags	2024-04-30 11:57:47 +00:00