Suggest remove the Extensions

[wjqdst]

trafficstars

Hi, Because now in the TaskDefinition have 2 EquatableDictionary parameter, 1 is Extensions another is Metadata, but if we use odata it will casue error, and I see in the document we just have Metadata do not have Extensions, so I suggest to remove the Extensions parameter. Thanks.

[evil116]

when will the issue be resolved? @cdavernas

[cdavernas]

@evil116 Not before next week as I'm in PTO. If that's a problem, you are welcome to open a PR 😉

On a side note, @wjqdst @evil116 please be so kind to star the project to show your support!

[wjqdst]

@cdavernas noted with thanks, when you work next week, please let us know whether your team will fix this and when will have a new release for this. 😉

[wjqdst]

@cdavernas may I know this progress

[cdavernas]

Still on PTO. As said, I'll try to solve it this week 😉 I'll keep you posted.

In the meanwhile, please do drop a star 🙏

[wjqdst]

noted, already drop.

[wjqdst]

@cdavernas may I know the progress again

[cdavernas]

Merging in progress.

On a side note, and even though the extensions property was not required anymore, the metadata one should NOT be considered as an ODATA extension property: unlike extensions, it should be queryable just like any other top level properties. To do so, you'd need to register EquatableDictionary<string, object> as a new complex type, or using a surrogate list type (ex: KvpList<T>)