anyone know what’s up with intellisense in SST projects?

environment

doesn’t show up as a property, but it should be. this might be a VS Code bug, seems like

Hmm.. I’ve seen a similar weird issue with IntelliSense https://github.com/serverless-stack/serverless-stack/issues/426

weird. mind if I add my case to that issue, since it could be related?

For sure!

I left a comment explaining it

Ah I see… do you have an example of the syntax? just to get a taste of how verbose it is 😅

Basically the gist is to be able to identify the specific type inside a union type, you need a way to "discriminate" between them. So all the types need a common field that can serve as the discriminator

type Rectangle = {
  kind: "square";
  width: number;
  height: number;
};

type Circle = {
  kind: "circle";
  radius: number;
};

type Shape = Rectangle | Circle

function test(s: Shape) {
  console.log(s.height) // type error
  if (s.kind === "square") {
    s.height // valid
  }
}

Oh nice.. I kinda like that 😂

I like it too, we can use it with

bundle

as well and have very nice developer experience where it shows them what options are available for a python bundle vs a go bundle

A problem with CDK so far is that the

instanceof

check is not reliable. ie. SST has the

@aws-cdk/aws-s3

dependency, and users can also have

@aws-cdk/aws-s3

as their dependency. If they are of different versions, the package is going to appear twice in side

node_modules

.

can peer dependencies help there?

Yeah we looked into that briefly.. forgot what the problem was. Yeah should look into it again.