Tsuf Cohen

better error message for compiling unknown platforms

3

### I tried this: I wanted to test wing code the awscdk target, I didn't have it installed on my machine. I ran: `wing test -t @winglang/platform-awscdk path-to-file` ### This...

### Use Case currently, we can't rename class properties, structs keys, and interface keys since it wasn't supported on #6461 ### Proposed Solution _No response_ ### Implementation Notes _No response_...

### Use Case Assume we want to customize namespace names, we can't since it's excluded from the regular rename refactor implementation- https://github.com/winglang/wing/blob/79bddc6a90fab2b3fc0c38fa30c61bcff0e11309/libs/wingc/src/lsp/rename_visitor.rs#L45-L49 since it needs a "customized" edit- `bring ex;`...

rfc: wing tests

2

fixes: https://github.com/winglang/wing/issues/5540 ## Checklist - [ ] Title matches [Winglang's style guide](https://www.winglang.io/contributing/start-here/pull_requests#how-are-pull-request-titles-formatted) - [ ] Description explains motivation and solution - [ ] Tests added (always) - [ ] Docs...

creating an rfc for testing

1

### Use Case following 25/01/24 team time - we can only make wing's testing framework great if someone owns it, I'll collect the relevant issues and try my best to...

fix(compiler): using `super()` in an inflight constructor compiles but fails at runtime

2

fixes: #6940 Compiled output of the `SuperClass` (slightly different class than the one in the example): Test results: ## Checklist - [ ] Title matches [Winglang's style guide](https://www.winglang.io/contributing/start-here/pull_requests#how-are-pull-request-titles-formatted) - [...

fix: expected type to be `Array<Json>`, but got `Array<Json>` instead

4

fixes #5421 in addition to the examples in the issue, I added one with `MutMap` (since it was also missing). I noticed that `Set` and `MutSet` aren't legal `Json` values,...

### I tried this: ``` let a: MutJson = {a: 1, b: 0}; let b = MutJson {a: 1, b: 0}; a.delete("a"); b.delete("a"); ``` ### This happened: ### I expected...

### I tried this: ``` let a: MutJson = {a: 1, b: 0}; let b = MutJson {a: 1, b: 0}; let c = {a: 1, b: 0}; let d:...

improve error message when accessing an optional map property

6

### Feature Spec Assuming we have an optional Map, and we want to access one of its properties, `optional_map.get("property")` (or even `optional_map?.get("property")`) will throw the following error: "property access unsupported...