Danny Tuppeny

According to the spec, everything will fall into "3. Definitely a getter-setter". If what you mean is "an explicit getter-setter", then (besides some possible exceptions with final/sealed classes) everything will...

> There could be a higher change of misinterpretation by colouring the fields the way they are, I'm not sure I understand the possible misinterpretation here. Currently, all of these...

Sorry for the delay in responding. We had some discussion about this yesterday and agree that we should make the behaviour across the tooling consistent with respect to properties and...

I found this odd too - you can't see which path was taken in code like this: Although IIRC the same is true for things like `var a = x...

> How are you running your tests, and what version of Dart are you using? Was this question for me or @FMorschel? For my example above, I was using `flutter...

@yahu1031 can you add details of exactly what functionality you're using (code links would be helpful too) so I can understand exactly what would need to be provided if "raw"...

@samyakkkk the problem with the internal APIs is that they are not designed for consumption and have no versioning. They frequently change (particularly when things are refactored) and will break...

> [To get the outline](https://github.com/Welltested-AI/dash-ai/blob/8b2790ab6d9342c90e26be6b48e5ac4ae9d25504/vscode/src/utilities/contextual-code.ts#L32). Can we keep the fileTracker and flutterOutlineTreeProvider exposed for this? I'm not against keeping it (and other things) there _for now_, but we should make...

Had a quick chat with @jacob314 about this earlier, who noted some of the APIs described above are not really VS Code-specific (for example asking for a list of simulators...

@tomgilder thanks! Those should be easy to handle - although some things worth noting: - The user can change their SDK while the extension is running (this triggers a reload...