I wrote a simple wrapper for Highcharts in the Pharkas style. It's almost a direct replacement for the official highcharts-angular component with currently just one unimplemented Input and one intentionally dropped "bag-in-box" Input/Output: update and updateChanged. update felt hugely redundant next to an Input already of Observable<Highcharts.Options> so I dropped it. Observable-only life!
It may also serve as another good example of real world Pharkas usage.
I don't want to add Leaflet directly as a peer dependency, however. So then we get into a question of: does it need a "satellite" library? How many libraries do I want to maintain? Or is it a case of too many small libraries missing the point?
I really wish Angular's packager didn't suck so much and didn't get so much in the way of useful tree-shaking so that I have to worry so much about peer dependencies for optional features.
I wrote a simple wrapper for Highcharts in the Pharkas style. It's almost a direct replacement for the official
highcharts-angularcomponent with currently just one unimplemented Input and one intentionally dropped "bag-in-box" Input/Output:updateandupdateChanged.updatefelt hugely redundant next to an Input already ofObservable<Highcharts.Options>so I dropped it. Observable-only life!It may also serve as another good example of real world Pharkas usage.
I don't want to add Leaflet directly as a peer dependency, however. So then we get into a question of: does it need a "satellite" library? How many libraries do I want to maintain? Or is it a case of too many small libraries missing the point?
I really wish Angular's packager didn't suck so much and didn't get so much in the way of useful tree-shaking so that I have to worry so much about peer dependencies for optional features.