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

removed CurrentPackage() since envy only support go module mode #39

Merged
merged 1 commit into from
Nov 3, 2021

Conversation

sio4
Copy link
Member

@sio4 sio4 commented Oct 30, 2021

As of v1.7.1 it supports go 1.13 or higher and as of v1.9.0 Mods() was technically deprecated. However, we still have CurrentPackge() and it should be deprecated since the result of the function is not meaningful anymore.

This PR could be a breaking change but I would suggest removing the function as soon as possible and then I will track if there are some broken packages within gobuffalo projects as an additional task of gobuffalo/buffalo#2152.

Fixes #37

@sio4 sio4 changed the title removed CurrentPackage() since it support go module mode only removed CurrentPackage() since envy only support go module mode now Oct 30, 2021
@sio4 sio4 changed the title removed CurrentPackage() since envy only support go module mode now removed CurrentPackage() since envy only support go module mode Oct 30, 2021
@paganotoni paganotoni merged commit 9d76507 into gobuffalo:main Nov 3, 2021
@sio4 sio4 deleted the deprecate-currentpackage branch May 14, 2022 15:58
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.

should CurrentPackage() be deprecated?
2 participants