Skip to content

fix: resolve relative paths when cwd differs from EIPs repo root - #154

Closed
Kubudak90 wants to merge 1 commit into
ethereum:masterfrom
Kubudak90:fix/issue-12-cwd-relative-paths
Closed

fix: resolve relative paths when cwd differs from EIPs repo root#154
Kubudak90 wants to merge 1 commit into
ethereum:masterfrom
Kubudak90:fix/issue-12-cwd-relative-paths

Conversation

@Kubudak90

Copy link
Copy Markdown

When linting files from a working directory different than the root of the EIPs repository, the preamble-requires-status check would fail with ENOENT errors because it tried to find required EIPs at relative paths like ./EIPS/eip-xxxx.md instead of the correct absolute paths.

This fix normalizes relative paths by joining them with the current working directory, ensuring required EIPs are found regardless of where the linter is invoked from.

Includes a regression test that reproduces the issue.

Fixes #12

When linting files from a working directory different than the root of
the EIPs repository, the preamble-requires-status check would fail with
ENOENT errors because it tried to find required EIPs at relative paths
like ./EIPS/eip-xxxx.md instead of the correct absolute paths.

This fix normalizes relative paths by joining them with the current
working directory, ensuring required EIPs are found regardless of where
the linter is invoked from.

Fixes ethereum#12
@Kubudak90
Kubudak90 force-pushed the fix/issue-12-cwd-relative-paths branch from 9f89249 to ff9deca Compare April 14, 2026 19:54
@Kubudak90

Copy link
Copy Markdown
Author

Closing in favor of #153 which takes a more comprehensive approach by normalizing the source path early, including WASM support.

@Kubudak90 Kubudak90 closed this Apr 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant