nested-main-bundle-ignore: Ignore Nested Obsidian Main Bundles #3
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "task/nested-main-bundle-ignore"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Assigned idea
Benchmark authoring specification.
Summary: Update the ESLint flat config so generated Obsidian
main.jsbundles are ignored even when they appear in nested plugin or vault directories, while preserving TypeScript linting.Task intent: Make an ordinary upstream-facing lint configuration fix in
eslint.config.mjs: the existing baremain.jsignore should cover generated Obsidian bundle files outside only the repository root, without weakening the TypeScript parser setup.Benchmark plan: Construct the task package as a small lint-config change request. The solver prompt should ask for nested generated
main.jsfiles to be ignored by ESLint while keeping the@typescript-eslint/parserproject configuration for**/*.ts. The package should include a verifier that checks the config text and dynamically confirms a nested generatedmain.jswith invalid JavaScript is skipped by ESLint.Environment plan: Task/environment: provide only the work prompt and
test_outputs.py; the verifier creates and removes a temporary nestedtmp-eslint-ignore/nested/main.jsfixture. Environment/repo: materializegreen-dalii/obsidian-llm-wikiatb327f87ff3b5e0e969d5e8e9c03e4a5f630e4ce2and install the repository's Node dependencies normally before running ESLint.Verifier plan:
test_outputs.pyshould readeslint.config.mjsand require an explicit nested-main ignore pattern such as**/main.js, preserveproject: "./tsconfig.json", preserve thenode_modules/ignore, and reject broad JavaScript ignores such as**/*.js. It should then createtmp-eslint-ignore/nested/main.jscontaining a syntax error and runnpx eslint --no-warn-ignored tmp-eslint-ignore/nested/main.js, expecting exit code 0 because the file is ignored.Oracle plan: The oracle solution edits only
eslint.config.mjs, changing the global ignore entry from a root-only baremain.jspattern to a nested-capable**/main.jspattern while leaving the Obsidian recommended config spread and the TypeScript parser options intact.Difficulty plan: Coding agents may over-broaden the ignore rule to all JavaScript files, remove the TypeScript project-aware parser block to avoid lint errors, or misunderstand ESLint flat-config glob semantics where a bare filename does not reliably cover nested generated bundles.
Repo patch scope: Expected upstream edit scope is limited to
eslint.config.mjs; no changes should be made to TypeScript source files, package metadata, lockfiles, or generated build outputs.Anti-leakage notes: Do not expose to solvers any mention of benchmark, harness, Snorkel, Harbor, std-ts, agent, stage, attempt, retry, generated task, or evaluation context.
Approach: Use the existing ESLint flat config as the target. Replace or supplement the current
main.jsignore with**/main.js, keepnode_modules/, and keep thefiles: ["**/*.ts"]TypeScript parser configuration using./tsconfig.json.Verification: Run
python test_outputs.py; it must inspecteslint.config.mjsand executenpx eslint --no-warn-ignored tmp-eslint-ignore/nested/main.jsagainst a temporary invalid nested bundle file.Risk: The dynamic ESLint check depends on repository dependencies being installed. Mitigate by documenting dependency installation in the environment setup and keeping the verifier focused on
eslint.config.mjsplus one temporary fixture.Path rules: task package is tasks/; mutable upstream checkout is tasks//task/environment/repo; benchmark package files are under tasks//task; verifier/container environment belongs under tasks//task/environment; regular and UI verifier logic belongs in task/tests/test_outputs.py and test.sh only runs that file through pytest.
Agent context
Task slug: nested-main-bundle-ignore
Branch: task/nested-main-bundle-ignore
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.