Skip to content

Say in the README that a replace directive cannot stand in for the import rewrite. #28

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
avgvi merged 1 commit into from
Oct 11, 2026
+5 −0
Merged

Say in the README that a replace directive cannot stand in for the import rewrite. #28

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,6 +50,11 @@ On Linux drop the `''` after `sed -i`. Tags up to v1.4.0 are upstream's and
declare the upstream module path, so v1.4.1 is the first version that resolves
under the new path.

A `replace github.com/jmoiron/sqlx => github.com/secondwindoss/sqlx v1.4.1`
directive does not work: the fork imports its own `reflectx` package under
the new path, and Go refuses to use one module under two paths. Rewrite the
imports instead.

## Recent Changes

1.4.1:
Expand Down
Loading