Closed skyrpex closed 3 months ago
@Chriscbr looks like this is related to modules, no?
I think it's just a typo, you wrote:
let resourceA = new resource_a.ResourceA();
let resourceB = new resource_a.ResourceA();
Should be:
let resourceA = new resource_a.ResourceA();
let resourceB = new resource_b.ResourceB();
I think it's just a typo, you wrote:
let resourceA = new resource_a.ResourceA(); let resourceB = new resource_a.ResourceA();
Should be:
let resourceA = new resource_a.ResourceA(); let resourceB = new resource_b.ResourceB();
Thanks, I fixed the typo in the issue.
Congrats! :rocket: This was released in Wing 0.74.33.
I tried this:
This happened:
The language server mistakes the QueueMessage from
resource-b.w
Wing compiles the
ResourceB
withResourceA
'sQueueMessage
! This is a quite serious bug since it can happen silentlyI expected this:
Each resource should use their own private scoped
QueueMessage
structs.Is there a workaround?
Renaming the structs.
Anything else?
No response
Wing Version
0.59.8
Node.js Version
No response
Platform(s)
No response
Community Notes