Skip to content
This repository has been archived by the owner on Jan 9, 2020. It is now read-only.

Update to quasar v1? #94

Open
cmichel21 opened this issue Aug 20, 2019 · 5 comments
Open

Update to quasar v1? #94

cmichel21 opened this issue Aug 20, 2019 · 5 comments

Comments

@cmichel21
Copy link

cmichel21 commented Aug 20, 2019

Quasar v1 has been released, eosdac-client is still on v0.17.

It seems to have quite some breaking changes. Has there been an effort yet to update to the new version?
I guess it will also break many existing eosdac-client-extensions?

Update guide

@michaeljyeates
Copy link
Contributor

We looked at v1 a few months ago and in the end decided that it wasnt worth updating yet.

@michaeljyeates
Copy link
Contributor

I think the summary was that the new features werent worth the major breaking changes

@str
Copy link
Member

str commented Aug 20, 2019

What about pushing the upgrade to a next milestone? Sooner or later the update will be needed.

@piecesnbits
Copy link
Collaborator

yeah I agree with @str it will be needed sooner or later. it's a lot of work though and if we decide to do it then a feature freeze on the client is needed.

@MrToph
Copy link

MrToph commented Aug 24, 2019

I agree that it is necessary to do (unless you plan to rewrite everything in a different framework). A major update is not only about the new features, but having the possibility to easily upgrade in the future in case of security issues / bug fixes / features.
And the longer an update is postponed and new features added on top of the old, the more needs to be done later.

Not to mention the documentation including the search for quasar v1 is so much better than for 0.17.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants