Joel Hendrix
Joel Hendrix
Closing per our discussion.
I see, I missed the `build.go` file, that does help. Is there a way to specify a different version of the code generator?
In the example, is the `"*"` a well-known concept for MSAL, or is this something we're inventing?
Should our API be explicit too (it's what we did in track 1)? Are there any downsides/risks with using a wildcard for the additional tenants?
I meant explicit in regard to only allowing a list of tenants, no wildcard (this is what we did in track 1). Regardless, it sounds like the wildcard is needed...
It would appear that the build is using a version of Go predating 1.18. Our build constraints are for Go 1.18+ ([example](https://github.com/Azure/azure-sdk-for-go/tree/main/sdk/azcore/policy)). We do build with 1.19 in our CI...
Does it repro from the command line too, or just in GoLand? I can build `azcore` locally so I'm at a bit of a loss. ``` PS D:\git\Azure\azure-sdk-for-go\sdk\azcore> git checkout...
No worries, hope you find the solution (I haven't used GoLand so I have no clue).
Thanks for the details, maybe this will help others that hit the same issue.
I see that the root `build.go` file was removed. While you don't have to fix it now, we really should ensure that all modules can be built via `go generate`.