alessandro vandelli

Ignoring errors is almost always a bad ideas. I had recently the same issue and i found that was caused by a bad css. My advice to try to solve...

Just created a small module declaration. Surely not the best... ``vue-numeric.d.ts`` ```ts declare module "vue-numeric" { import Vue from "vue"; interface VueNumeric extends Vue, HTMLInputElement { props: { currency: string;...

I have the same error in my project. I'm trying to recreate a drag and drop feature inside a group of tables. So i have nested layers something like: ```html...

Yeah but still remais undefined. Check #561

Basically what @zhaolei2013 states is true. I had the same problem and I was not able to find a way to retrieve that value. My workaround is to use the...

I have a similar issue, in my case I've created a chart used to compare data in time. The series names are the same "measureName+deviceName" but in the end they...

Nice workaround but I'm developing an app that must render dynamic charts with dynamic data. I don't know how many series/yaxis/xaxis there will be at the end. I'm currently patching...

My previous screenshot only had 2 series. I'm already using the type "scroll" for legend. This helps but it still is just a workaround. We also have that same issue...

@minhnhat44 Be careful with your suggestion. If the user/db uses a "dashed-name" it will break your logic, ex: ```ts const name='dashed-name-id1'; const nameWithoutId=name.split('-')[0]; // => "dashed" ``` If you want...

I tried to use some of the code inside this PR for one of my projects and I've noticed that both "guacamole-touchscreen" and "guacamole-touchpad" didn't fulfill all the requirements to...