Skip to content

Add vscode style ".acode" folder and file structure for settings and extensions. - #3093

Open
codewithchai0605 wants to merge 5 commits into
Acode-Foundation:mainfrom
codewithchai0605:feat/acode-workspace
Open

codewithchai0605 wants to merge 5 commits into
Acode-Foundation:mainfrom
codewithchai0605:feat/acode-workspace

Conversation

@codewithchai0605

Copy link
Copy Markdown
  1. Plugin recommendations.
  2. Project settings

Plugin recommendations.
A project can suggest plugins that suits it. This is only ever a suggestion nothing here installs, enables or runs anything.
it can be used like this, Plugin recommendations: the contents of .acode/extensions.json
{ "recommendations": ["acode.plugin.example"] }

Note: This requires the backend to update the existing search api to also accepts query like "id:plugin.id" like "mode:pluginId".

Project settings:

It allows to change the project level settings without editing their globals settings.

This feature is not implemented completely. It can be improved much.

- Implement tests for workspaceExtensions including validation of plugin IDs, parsing of extension recommendations, and handling of hostile input.
- Introduce tests for workspaceSettings covering project settings allowlist, parsing of project settings, and validation of individual settings like tabSize and formatOnSave.
- Ensure both test files check for frozen results and handle edge cases such as invalid JSON and prototype pollution.
@github-actions github-actions Bot added enhancement New feature or request translations Anything related to Translations Whether a Issue or PR labels Nov 17, 2026
@greptile-apps

greptile-apps Bot commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

RetriggerView in GreptileConfidence Score: 5/5

[Medium impact] The reviewed changes appear safe to merge; both previously reported problems are fixed.

Summary

Adds project-level settings and plugin recommendations through a .acode folder without changing global preferences or installing plugins.

  • Acode tracks open projects that have a .acode folder.
  • Files in a project can use editor settings from its .acode/settings.json.
  • Acode offers a review search for plugins a project recommends.

Both numbered findings from the previous review are addressed. No new actionable issues were found.

Reviews (7) · Last reviewed commit: "Enhance EditorManager and workspace func..." · Reviewed by Greptile

Comment thread src/lib/editorManager.js Resolved
Comment thread src/lib/workspace.js Resolved
Comment thread tests/unit/projectExtensions.test.js Resolved
@codewithchai0605

This comment was marked as outdated.

Comment thread src/lib/openFolder.js Resolved
@codewithchai0605

This comment was marked as outdated.

1 similar comment
@codewithchai0605

This comment was marked as outdated.

Comment thread src/lib/editorManager.js Resolved
Comment thread src/lib/workspaceSettings.js Resolved
Comment thread src/main.js Resolved
Comment thread src/main.js Resolved
Comment thread src/lib/commands.js Resolved
@codewithchai0605

This comment was marked as outdated.

Comment thread src/lib/workspace.js Resolved
Comment thread src/lib/editorManager.js Resolved
@codewithchai0605

This comment was marked as outdated.

@codewithchai0605

Copy link
Copy Markdown
Author

@bajrangCoder

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request translations Anything related to Translations Whether a Issue or PR

Projects

Status: Backlog

Development

Successfully merging this pull request may close these issues.

1 participant