-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Refactor: Split socket_spec.cr into separate files #6700
Refactor: Split socket_spec.cr into separate files #6700
Conversation
spec/std/socket/address_spec.cr
Outdated
end | ||
|
||
describe ".unix" do | ||
it "creates a unix socket" do |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why this landed to address_spec.cr
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
after looking at the rest, it looks like you forgot to remove these specs from this file, ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Darn, looks like something went awry during rebase. These specs are supposed to be only in spec/std/socket/socket_spec.cr
. I'll fix it.
spec/std/socket/address_spec.cr
Outdated
end | ||
end | ||
|
||
it ".accept" do |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ditto
All CIs failed with this:
|
be83d8b
to
3422a1b
Compare
@RX14 yay, the issue with Unix socket path limitation with MacOS's temp dir is back: https://circleci.com/gh/crystal-lang/crystal/12013?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link |
f1fef04
to
3331d34
Compare
3331d34
to
bb45203
Compare
This PR splits the large monolithic
socket_spec.cr
into separate files for the individual components. This makes it easier to follow the specific component specs in their own context and improves overall readability by segregating individual features.This is the first in a series of PR's to improve the Socket API.