Automattic / Automattic/harper

I think the Obsidian plugin maybe can't handle the `OneOfMany` linter config type

Open
#4,218 1 comment 0 reactions 0 assignees View on GitHub
bug ci good first issue harper.js obsidian-plugin
Dominant language
Rust
Stars
15.4k
Forks
627
Avg merge
1d 15h
Merged PRs (30d)
102

Description

My PR #4211 passes all `cargo test` for rust but keeps failing in the Obsidian integration.

I'm not doing to well trying to understand the error messages so I'm not positive but I'm tending toward thinking that when the `OneOfMany` config type was introduced that support for it might not have been added as needed to the Obsidian plugin.

Both CoPilot here on GitHub and the free AI agent in my editor (Devin) seem not to have been able to figure out why there are failures in the Obsidian integration.

Because the Obsidian plugin uses `harper.js` the problem could be there or in the WASM?

Contributor guide

Open the contributing guide

Research direction

Start with PR #4211 and run the Obsidian integration alongside the passing cargo test suite to capture the failure. Trace whether OneOfMany support is missing in the Obsidian plugin, harper.js, or the WASM boundary; done means the Obsidian integration passes with this config type.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, rust, wasm
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.