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.

Sign up for GitHub

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

Jump to bottom

change new Boom() to new Boom.Boom() #253

Closed
hueniverse opened this issue Sep 28, 2019 · 1 comment
Closed

change new Boom() to new Boom.Boom() #253

hueniverse opened this issue Sep 28, 2019 · 1 comment
Assignees
@hueniverse
Labels
breaking changes Change that can breaking existing code
Milestone
8.0.1

Comments

@hueniverse
Copy link
Contributor

Moving away from direct exporting of classes and functions as public API. Should not affect most users as new Boom() is rarely how people should use the module.
@hueniverse hueniverse added the breaking changes Change that can breaking existing code label Sep 28, 2019
@hueniverse hueniverse added this to the 8.0.1 milestone Sep 28, 2019
@hueniverse hueniverse self-assigned this Sep 28, 2019
@lock
Copy link

lock bot commented Jan 9, 2020

This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@hueniverse hueniverse

Labels
breaking changes Change that can breaking existing code
Projects
None yet
Milestone
8.0.1
Development

No branches or pull requests
1 participant
@hueniverse