You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At one point of the solution, it just seems ideal to refactor and distribute the codes into various files.
But testing of these files are not supported.
In my case where I'm using go , I have to keep all my code within main.go.
The reason to my understanding is the following code in your_program.sh.
# this is the current included code
go build -o /tmp/codecrafters-build-grep-go cmd/mygrep/main.go
# something like this would be more helpful
go build -o /tmp/codecrafters-build-grep-go ./cmd/mygrep/...
I would like to know if this behavior of keeping all the code in just one file is by design, and if so what is the main idea behind it?
The text was updated successfully, but these errors were encountered:
We'll take a look at this! In the meantime, you should be able to change the files in .codecrafters/{compile/run}.sh to get the tester to include your files.
At one point of the solution, it just seems ideal to refactor and distribute the codes into various files.
But testing of these files are not supported.
In my case where I'm using go , I have to keep all my code within
main.go
.The reason to my understanding is the following code in
your_program.sh
.I would like to know if this behavior of keeping all the code in just one file is by design, and if so what is the main idea behind it?
The text was updated successfully, but these errors were encountered: