Cryptic Error Message when generating module
See original GitHub issueWhen generating a module we are getting the error message
PLUGIN FAILURE: Cannot read property 'enum' of undefined, TypeError: Cannot read property 'enum' of undefined
Any clues or pointers regarding the cause of the error?
Full Log Attached here
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
6.4.0: ng g lib produces "Path does not exist" cryptic error ...
Either changing "newProjectsRoot" or removing the "schematics" key from angular.json solved it. Steps to Reproduce. n/a. Context. $ ng --version ...
Read more >Issue 39665: Cryptic error message when creating types that ...
I was trying to create a class that didn't have any references to itself to test issue39382 and ran the following code: class...
Read more >Cryptic Error message on Javascript module import
The static import statement is used to import bindings which are exported by another module. Imported modules are in strict mode whether you ......
Read more >Working with cryptic error messages from ReasonML when ...
Instructor: [00:00] Here I've got a module that implements a custom Decco codec, but there's a compiler error. It's pretty confusing. Let's go ......
Read more >Cryptic Error When Attempted to Sign Kernel Modules
I am trying to sign and load a new kernel module for virtualbox. I generated a certificate and private key using openssl req...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@peombwa, I try to use the autorest.powershell, which I built from msgraph branch. I still could not reproduce the issue mentioned by @georgend. And in my side, it reported another issue in autorest/core. For autorest/core issue, I will need to move it to autorest repo, which is owned by autorest team.
@georgend, the issue was with how the key segment parameter object was defined in the OpenAPI file as described in https://github.com/microsoftgraph/microsoft-graph-devx-api/issues/902#issuecomment-1062443630.
We can close this issue since this has already been fixed in the OpenAPI file. A complete support will be provided by https://github.com/Azure/autorest/issues/4480.