Isn’t

sst start

supposed to update the functions (

sst.Api

) live when saving? Right now I can see the console processing after save, but running the function again does not show the changes. Currently, we’re stopping and restarting sst cli in order to see changes. This can’t be whats supposed to happen?

yeah this sounds like a bug, your lambda code is inside the same folder as your stacks right?

ya… a co-worker had the same issue last week and I thought it was just on his machine but now I’m having the issue too….. same repo though, so you could be right about the stacks and functions together being the issue.

Yeah it's definitely tempting to colocate everything but ultimately infra code is very different than application code even though they're in the same language. Leads to some tricky situations

ya feels like it should be allowed…. so long as your not cross-importing lambda and infra code. I just want the “folder” structure to be coupled with the constructs associated

I have a quick fix for your issue which I'll push out today

oh…. shit…. I’m just reorgin everything to fall in line 😛

Well, I still recommend that

kk

It's the same logic as having tests next to the files they're testing vs in a seperate directory. For example

src/module.ts
src/module.test.ts

vs

src/module.ts
test/module.test.ts

It can be nice to have everything colocated and there's good arguments for that. The arguments against it is the boundaries aren't as clearly defined and it's easy to intermix things that shouldn't be. And you can always use editor plugins to jump to the test from the module

oh weird…. that uses diff tsconfig for lambdas (backend) and cdk

You can still share one if you want

See any issues sharing a

config.ts

of (static config values) file between CDK and Lambdas?