Angular CLI 1.5.4
Angular 5.0.3
Node: 8.2.1
OS: OS X Sierra 10.12.6
Wijmo: 20173.380 amd-src
WARNING in Circular dependency detected:
libs/wijmo/wijmo.chart.ts → libs/wijmo/wijmo.chart.ts
WARNING in Circular dependency detected:
libs/wijmo/wijmo.gauge.ts → libs/wijmo/wijmo.gauge.ts
WARNING in Circular dependency detected:
libs/wijmo/wijmo.grid.ts → libs/wijmo/wijmo.grid.ts
WARNING in Circular dependency detected:
libs/wijmo/wijmo.input.ts → libs/wijmo/wijmo.input.ts
WARNING in Circular dependency detected:
libs/wijmo/wijmo.ts → libs/wijmo/wijmo.ts
I’m just gonna rant for a bit, don’t bother replying if all you have to say is “sorry we can’t replicate the issue here’s an example that uses different versions / build tools and doesn’t come close to resembling a practical project structure”.
A. I’ve had this product for almost 1 year, every time I go to use it I run into problems that all sum up to the fact that the way it is packaged is not at all standard or commonplace and as such never plays nice with anything else other than your sandbox in which you ‘cannot replicate the issue’
B. From my first attempt to use Wijmo through the very latest release there has ALWAYS been a difference in amd-src vs amd-min! Does not matter whether I’m using webpack or ngcli, I get errors in src that I don’t see in min… it’s infuriating!
C. The project structure of each and every example/sample you provide is horrid, and it should be embarrassing. You only have app.ts and treat it like component, module, barrel, and sometimes even service. Often times the specific topic of an example will not even include critical logic in the showcase component because it’s buried somewhere else in the samples package as a base class/component which is extended by, and is convulated with logic to accommodate, every single other component in the samples library. Many of your examples ship pre-transpiled and rely on the js for the example to actually work - if I delete the js and let the compiler do its thing the sample won’t recover. All of this and you’d imagine it can’t get much worse - but to ice the cake I’ll mention that even though the samples double as the component explorer (meant to showcase ease of use!) they are so poorly formatted and contain so few comments in code that it’s a chore to understand whether each method, property, etc of the super base component is pertinent to your desired functionality or whether it’s there for something unrelated to what you’re after.
D. It’s a bit disingenuous to continue touting world-class angular support, easiest ever components with declarative blah blah who gives a damn when it takes my otherwise well behaved projects and litters the console with warnings (at best) and, if this particular Wijmo release feels like it, errors which prevent build completion. I’ve mentioned this is another post a long while ago but your chosen method of releasing the commercially licensed code is not at all sufficient. Take a page from Telerik’s book and adopt the same methods they use to expose commercially licensed code… it works MUCH better and while their components aren’t quite to the same marketed level as yours they have one significant advantage… I CAN USE IT!
E. Hire a developer and ask him to build some good example projects with your components using nothing but wijmo-docs, wijmo-examples, and this very forum. … Now, when he quits after a couple of weeks because he can’t build a damn thing, take one of your ninjas from your dev team and make it his mission to simply build cool shit with the wijmo library using the same dev environments and build tools the rest of the world uses. Hopefully he’ll get pissed off enough to change the way you do things and he’ll be equipped to do so because of his previous experience on the dark side. If he asks to use your home-baked sandbox that apparently produces never-ending flawless builds regardless of ngcli/webpack/angular/wijmo/typescript version then fire him immediately and try again with someone else. If he tries to shortcut 75% of the value from example code by not annotating with notes/comments or by wiring 65 separate examples together with one ridiculously impractical base component then conjure up some really comical creative way to fire him because he deserves it.
You guys make some bad ass components, I REALLY want to use them in every project I’m doing but every single time I try I lose a week of productivity wrestling around with just getting it to integrate without breaking the rest of the project. You need to start releasing those bad ass components in a more consumable manner, and you don’t have to re-invent the wheel to do it… start here with any of the following…
"
