Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1935
Thanks for GREAT suggestions @1ambda.
>It would be great if helium package has version field considering local
package and latest
I've just added `version` and `published` field to each pkg version's
information. Please check
[helium.json](https://s3.amazonaws.com/helium-package/helium.json)(used for
Zeppelin Helium GUI menu) and
[helium.js](https://s3.amazonaws.com/helium-package/helium.js)(used for
zeppelin.apache.org). I also added `published` date for each version, to show
latest package first. So now, it'll be look like below
```
"0.0.3": {
...
},
"latest": {
"type": "VISUALIZATION",
"name": "zeppelin-bubblechart",
"version": "0.0.4",
"published": "2017-01-23T20:42:34.373Z",
"artifact": "[email protected]",
"author": "leemoonsoo",
"description": "Animated bubble chart",
"license": "BSD-2-Clause",
"icon": "<svg viewBox='0 0 70 70'><circle cx='26' cy='28'
stroke='black' style='stroke-width: 1px;' r='25' fill='seagreen'/><circle
cx='42' cy='44' stroke='black' style='stroke-width: 1px;' r='20'
fill='DodgerBlue'/><circle cx='54' cy='24' stroke='black' style='stroke-width:
1px;' r='15' fill='crimson'/></svg>"
}
```
And here is the latest update.
>If once people start to develop packages, there must be operational things
like user complains. For example, "I published package to npm, but it's not
collected by helium for last 2 days. What's the problem?" So, it's good for
each package to have some information for debug and ops like createdAt,
heliumFormatVersion.
Especially for this, totally agree with you. Actually there are lots of
things to be improved and can be changed. So I need more time to rethink about
how I can do that in Lambda function side. But as it doesn't affect directly to
merge this PR, I'll update it later time if it's okay with you. Appreciate
again!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
