[1.1.0] Namespace missing for an inner message
See original GitHub issueI noticed that with the 1.1.0 version, below proto is generated incorrectly:
message MessageOuter {
message MessageInner {
}
repeated MessageInner someProp = 1;
}
Generated d.ts is resulting in:
export class MessageOuter extends ... {
getSomeProp(): Array<MessageInner>; // #1
setSomeProp(value: Array<MessageInner>): MessageOuter // #2
...
}
export namespace MessageOuter {
...
export class MessageInner extends ... {
...
}
...
}
that will not compile, as the MessageInner should be prefixed with the namespace at #1 and #2. 1.0.7 used to generate this code just fine.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
c# - Type or namespace name does not exist - Stack Overflow
I have a WCF Data Service project built with Visual Studio 2010, which was working fine. All of a sudden, it didn't compile...
Read more >NuGet Restore task fails for .Net Core project migrated with VS ...
Dear all, I have .Net Core project which has been converted with Visual Studio 2017. The build plan especially the task NuGet Restore...
Read more >MissingManifestResourceExcepti...
Initializes a new instance of the MissingManifestResourceException class with a specified error message and a reference to the inner exception that is the...
Read more >Simple Object Access Protocol (SOAP) 1.1 - W3C
It MUST discard messages that have incorrect namespaces (see section ... All immediate child elements of the SOAP Header element MUST be ...
Read more >C# Error CS0246 – The type or namespace name 'type ...
Reason for the Error ... You will most likely receive this error when the C# compiler has not found the type or the...
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 Free
Top 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
Looks like this is due to #780. A fix for another purpose might have broken this. So perhaps a re-factor somewhere needs to be done.
I have a couple of fixes I’d like to do and get them in together, so hopefully next week.