search

eosdac / eosdac-client-legacy

This is the frontend to interact with the DAC smart contracts.
MIT License
14 stars 19 forks source link

Update to quasar v1? #94

Open cmichel21 opened 5 years ago

cmichel21 commented 5 years ago

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 commented 5 years ago

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

michaeljyeates commented 5 years ago

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

str commented 5 years ago

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

piecesnbits commented 5 years ago

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 commented 5 years ago

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.