David Brownman

This is a little bit out of the purview of our team (the editor team decides how our input is shown to end-users) but I can pass it along to...

The editor team confirmed this was a bug and I've filed it with them. We'll let you know here when it's closed (which may take some time).

@codebycaleb do you have a screenshot of how dire the error messages look? Trying to gauge severity here. And does this only affect CLI apps which _separately_ use bluebird promises?...

ok, cool! Good to know. Yeah, it's the first I've heard of it too. We'll keep this open in case other people have the same issue, but it doesn't strike...

@wwahammy Thanks for this question! I've got an answer in two parts: Firstly, I've run this by our legal team for clarification. We'll report back when they have an answer....

Hey @wwahammy! I'm no longer working at Zapier, so I can't speak to it anymore. I'm not sure who gets notifications on issues these days, but going through https://developer.zapier.com/contact is...

Thanks @om4csaba! I'll take a look. In the meantime, you can use [email protected] until we can release a fix for this.

ah, that's a bug! I can fix it. You'll still want to make sure the fields returned by `myChildDynamicField` have unique keys, but the static checker won't flag them for...

You can reuse the function, you just want to avoid this: ```js fields: [ { key: 'name' }, children: [ () => { key: 'name' } ] ] ``` Though,...

Ah ok, I realized what's going on. The actual issue is that the `children` field, by definition, can't have dynamic fields. The [schema](https://github.com/zapier/zapier-platform/blob/zapier-platform-schema%4011.2.0/packages/schema/docs/build/schema.md#properties-17) specifies that it only allows `field` objects....