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

support for Windows builds in make install step #80

Closed
wants to merge 11 commits into from
Closed

support for Windows builds in make install step #80

wants to merge 11 commits into from

Conversation

syke99
Copy link
Contributor

@syke99 syke99 commented May 22, 2022

This PR adds support for the install step on Windows for preparation of supporting Windows development.

theeyed and others added 2 commits May 22, 2022 21:41
* return 204 on nil error response

* allow void view actions

* fix controller test for 204 nil error response

* Fix `TestEmptyActionWithView`
@syke99 syke99 changed the title support for Windows builds in install step support for Windows builds in make install step May 22, 2022
Makefile Outdated
Comment on lines 12 to 18
ifeq ($(OS), Windows_NT)
cd livebud
npm install
cd ..
else
(cd livebud && npm install)
endif
Copy link
Contributor

@matthewmueller matthewmueller May 23, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
ifeq ($(OS), Windows_NT)
cd livebud
npm install
cd ..
else
(cd livebud && npm install)
endif
@ # Note: We don't use a subshell here to support Windows. See #79.
cd livebud
npm install
cd ..

I'd like to avoid conditionally checking the OS if we can. Since the windows version also works on linux and mac, let's just use that. I also just added a note to my future self not to accidentally change it back 😅

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Definitely understandable!! I just pushed up that change 😋

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @syke99! By the way, next time you can just hit the "Commit suggestion" button if the change works for you 😌

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ahh, didn't even see that option until now 😂 Thanks, I'll use it next time 😋

theeyed and others added 4 commits May 23, 2022 13:35
* return 204 on nil error response

* allow void view actions

* fix controller test for 204 nil error response

* Fix `TestEmptyActionWithView`
… and views (#84)

runtime/command/new/controller: Fix links when generating controllers and views. Closes: #82
@matthewmueller
Copy link
Contributor

matthewmueller commented May 23, 2022

For some reason this PR contains a6a8b12

Could you maybe rebase and push back up?

Makefile Outdated
@@ -9,7 +9,10 @@ precommit: test.dev
install:
go mod tidy
npm install
(cd livebud && npm install)
# Note: We don't use a subshell here to support Windows. See #79.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be tabbed and be prefixed with @ so it doesn't show up when you run make install

@syke99
Copy link
Contributor Author

syke99 commented May 23, 2022

Okay, repo has been rebased, comment corrected in Makefile, and changes pushed up~~ 😋

@matthewmueller
Copy link
Contributor

matthewmueller commented May 23, 2022

Hey @syke99, still seeing a bunch of files being updated. Maybe it's easier to close this PR, pull latest and open a new one?

@syke99
Copy link
Contributor Author

syke99 commented May 23, 2022

Sounds good, not sure why those commits are tagged to this PR. But I'll get a new one out!!

@syke99 syke99 closed this May 23, 2022
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.

3 participants