Skip to content

fix: update unit tests and fix incorrect module path imports#49

Closed
GeeDook wants to merge 4 commits into403unlocker:mainfrom
GeeDook:main
Closed

fix: update unit tests and fix incorrect module path imports#49
GeeDook wants to merge 4 commits into403unlocker:mainfrom
GeeDook:main

Conversation

@GeeDook
Copy link
Contributor

@GeeDook GeeDook commented Feb 1, 2026

It needs to be fixed in order to be packaged.

@SalehBorhani
Copy link
Collaborator

For more details i ask:

  1. Why we need this change ?
  2. Which issue does this PR address ?

@GeeDook GeeDook changed the title Fix addresses. fix addresses. Feb 2, 2026
@GeeDook GeeDook changed the title fix addresses. fix: update unit tests and fix incorrect module path imports Feb 3, 2026
@GeeDook GeeDook closed this Feb 3, 2026
@GeeDook GeeDook reopened this Feb 3, 2026
@GeeDook
Copy link
Contributor Author

GeeDook commented Feb 3, 2026

For more details i ask:

1. Why we need this change ?

2. Which issue does this PR address ?

The module path in go.mod must match the actual import path users need to use. Since our code is located in a subdirectory of the repository, the module path must include that subdirectory prefix.

Previously (incorrect): module 403unlocker-cli
Now (correct): module github.com/403unlocker/403unlocker-cli/subdir

This fixes the "invalid module path" error when running go mod commands.
resource: https://go.dev/ref/mod#module-paths:~:text=Module%20paths%C2%B6,of%20a%20test.

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.

2 participants