Closed thinkbeforecoding closed 4 years ago
The build is failing during dotnet-setup... I don't know what has changed there... ... after a few tests, I used the @v1 tag, and it's working 👍
he build is failing during dotnet-setup... I don't know what has changed there...
looks like temporary issue, after re-run all builds passed
I actually had to change actions/set-dotnet to @v1 to make it run. Seems the specific commit that was used previously doesn't work anymore.
This is actually a very small PR since almost everything was already in place. @dsyme , is it possible to merge it soon, since it's needed for the WsdlProvider (it starts to work very well by the way 😄)
This PR also includes a fix for #333 The TypeBuilder used to build Generic/Array/Pointer types was generating SymbolTypes even when both the GenericDef and the type parameter were classic .net types. This caused a problem when checking Type equality. The change now use typedef.MakeGenericType(args) to generate a classic .net type.
@sergey-tihon , @dsyme is it possible to merge this PR ? Is there more work to do on this ?
@cartermp can we merge this?
This appears to break my project, which uses generative type providers.
The not so useful error: https://github.com/deneuxj/SturmovikMission/runs/647494055?check_suite_focus=true#step:5:70
Building with 41b91efaaaebe2782472b283c0c716cbcb0bbe75 instead works.
There was no way to add custom attributes on ProvidedFields yet. It was required to add XmlEnum attribute on generated Enum fields for the WsdlProvider.
The change is minor (adding the AddCustomAttribute method), and test have been added.