Skip to content

Ember support #961

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

Merged
merged 1 commit into from
Aug 22, 2022
Merged

Ember support #961

merged 1 commit into from
Aug 22, 2022

Conversation

karadzhov
Copy link
Contributor

No description provided.

@karadzhov karadzhov marked this pull request as ready for review August 17, 2022 09:54
Copy link
Collaborator

@jakubjanecek jakubjanecek left a comment

Choose a reason for hiding this comment

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

Thank you for your contribution. In general, this is fine, I'd just like to avoid any incompatible changes unless really necessary - so for example the package renames could be avoided. I know it's not perfect but it's better than bugging the users. Could you please update it?

@karadzhov
Copy link
Contributor Author

Actually I didn't rename anything at first but then I thought - wouldn't there be some collision if both clients end up in one project as dependencies? What do you think?

@jakubjanecek
Copy link
Collaborator

Sure, so let's put the new implementation into separate package but let's keep everything already existing where it was. OK?

@mergify mergify bot merged commit 412a6ef into avast:master Aug 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants