Michel Boudreau

Definitely agree with this. In the meantime, I've adopted this not overly ideal pattern: ``` @Prop({attribute: 'data'}) dataAttr: string; @Prop({reflect: false}) data: any[]; @Watch('dataAttr') onDataChange(value: string) { this.data = JSON.parse(value);...

Is there any updates on this? I've updated `@actions/core` to the latest version as mentioned in the blog, but I'm still seeing this warning everywhere. Does the runner need to...

:cowboy_hat_face: I'd love to fix this, however as per the blog, [I've already updated `@actions/core` to the latest version](https://github.com/atlassian/gajira-create/blob/v3/package.json#L17) as mentioned already in the latest release, but it's still showing...

I was wondering when webhooks were going to pop up as an issue, so congrats on that :) First off, before we go into solutions mode, I'm curious as to...

Thanks for getting back to me quickly. Okay, so now I'm curious as to why you're using a callback when it sounds to me that you're just getting the response...

It's not that it's that unique. We've talked about it internally a while back as to what we'll support; for now we've only concentrating on http requests while we're redoing...

Not sure I'm understanding your dilemma, could you please try to explain it better? Maybe a quick diagram would help. On Fri, Apr 29, 2016, 2:14 PM Mike Farah [email protected]...

I'm in the same boat as Beth. Consumer's shouldn't care about the data that's not there, they should only care about their own data. If you want to do change...

Yeah, I get what you're saying. I don't have a particular problem with it as long as it's its own type and not the default. There's some interesting things you...

Can you confirm that the exact same code works as intended with DynamoDB? Can you past all the code related to your problem? On Tue, Sep 17, 2013 at 10:13...