Skip to content
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.

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

remove test gin dependency #369

Closed
wants to merge 1 commit into from
Closed

Conversation

tychoish
Copy link

No description provided.

@tychoish
Copy link
Author

sup nhooyr! :)

@tychoish
Copy link
Author

@nhooyr
Copy link
Owner

nhooyr commented Feb 15, 2023

@tychoish Hey Sam!

This test intentionally imports and tests gin. There's other end to end tests (or they might be only in the dev branch).

Gin is a terrible piece of software but widely used and it changes the behaviour of http.ResponseWriter which is why I felt the need to test against it directly.

But given the stupidity of go modules including test modules in downstream dependencies, I'll move the gin test into a different repository entirely eventually.

For now, master can't have anything merged into until I deal with #256

@tychoish
Copy link
Author

That makes sense. I've had some luck with having x/<foo> packages with their own sub-modules to isolate dependencies for cases kinda like this. It works... fine (with the annoying side effect of making go test ./... skip things you wish it didn't, but you can get around it with a little find/xargs magic). Anyway, seems reasonable.

Is there something technical blocking #256, or just time? Is there some work I (or someone) could do to help out?

@nhooyr
Copy link
Owner

nhooyr commented Mar 7, 2023

That makes sense. I've had some luck with having x/ packages with their own sub-modules to isolate dependencies for cases kinda like this. It works... fine (with the annoying side effect of making go test ./... skip things you wish it didn't, but you can get around it with a little find/xargs magic). Anyway, seems reasonable.

Good to know it works.

Is there something technical blocking #256, or just time? Is there some work I (or someone) could do to help out?

Failing tests. I appreciate your initative but it's something I need to review and fix myself.

@nhooyr nhooyr closed this Mar 7, 2023
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.

None yet

2 participants