483 implement javascript feature into extension to support custom javascript

[dharmesh-hemaram]

No description provided.

[nx-cloud]

View your CI Pipeline Execution ↗ for commit e96dfee

Command	Status	Duration	Result
nx affected --target=typecheck --parallel=3 --v...	✅ Succeeded	18s	View ↗
nx affected --target=test --parallel=3 --verbos...	✅ Succeeded	11s	View ↗
nx affected --target=lint --parallel=3 --verbose	✅ Succeeded	24s	View ↗

---

☁️ Nx Cloud last updated this comment at 2025-07-27 08:18:14 UTC

[Copilot]

Pull Request Overview

This PR implements JavaScript feature support into the extension to support custom JavaScript execution. The change enables users to create and execute JavaScript code snippets directly within the extension through a new "userscript" action type alongside existing action types.

Key changes include:

• Added support for custom JavaScript execution through a new userscript action type
• Restructured global extension state from individual window properties to a centralized window.ext object
• Updated Google Sheets integration to use the new extension state structure

Reviewed Changes

Copilot reviewed 64 out of 68 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
packages/core/extension/src/lib/background/chrome/messenger/user-scripts.messenger.ts	Implements userscript execution functionality with Chrome's userScripts API
packages/core/common/src/lib/model/core-model.ts	Defines IExtension and ISheets interfaces for centralized extension state
packages/acf/common/src/lib/model/IUserscript.ts	Defines IUserScript interface and default userscript template
apps/acf-options-page/src/app/configs/action/userscript-row.tsx	React component for rendering userscript rows in the action table
apps/acf-extension/src/content_scripts/userscript.ts	Content script processor for executing userscripts
Multiple files	Updates to use centralized window.ext object instead of individual window properties

Comments suppressed due to low confidence (3)

packages/core/extension/src/lib/background/chrome/messenger/user-scripts.messenger.ts:31

• The function name 'Notify' should follow camelCase convention and be more descriptive. Consider renaming it to 'notifyUserScriptsUnavailable'.

function Notify() {

packages/core/extension/src/lib/background/chrome/messenger/user-scripts.messenger.ts:33

• The variable name 'defaultOptions' is generic. Consider renaming it to 'notificationOptions' to better describe its purpose.

  const defaultOptions: chrome.notifications.NotificationCreateOptions = {

packages/acf/util/src/lib/value.ts:6

• The interface name 'IValue' is too generic and doesn't clearly indicate its purpose. Consider renaming it to something more descriptive like 'IExtensionWithApi' or 'IExtendedExtension'.

interface IValue extends IExtension {

[sonarqubecloud]

Quality Gate passed

Issues
2 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.1% Duplication on New Code

See analysis details on SonarQube Cloud

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
Report missing for 92a8b031	✅ 5.88%

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (92a8b03)	Report Missing	Report Missing	Report Missing
Head commit (e96dfee)	1820	120	6.59%

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#625)	51	3	5.88%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

Footnotes

1. Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct. ↩