how can I set a function base path for a bunch of routes in a

sst.Api

? so I don’t have to do:

'GET /folders': 'lambda/rest/functions/get-folders.main',
  'GET /global-search': 'lambda/rest/functions/global-search.main',
  'GET /tags': 'lambda/rest/functions/get-tags.main',
  'GET /trash': 'lambda/rest/functions/get-deleted-items.main',

way back in the early days of SST, I wrote a messy helper function to handle this for me. but now I need to get rid of that as it’s.. well, a mess, and there’s probably a better way now 🙂

String template literal 😁

hmm. yeah, I mean it’s not ideal, but that’ll work of course

I know, was being cheeky. 😄

haha I read that as "have you tried...variables?"

I think that’s fair 😄

tbf variables are pretty good and sometimes the simplest answer is the best

Being serious for a moment, it is something I’ve thought about and anything more than specifying the base path as a string template literal just gets complex quickly and there’s just not the ROI for something that doesn’t change (at least for us) very often

yeah I suppose so. not a huge deal.. doing a mass search/replace then 🙂

'([\w-]+)\.main'

-> ``${restFuncBasePath}/$1.main``

You can define one in the

defaultFunctionProps

object of the Api construct like this

const myApi = new sst.Api(this, "myApi", {
  defaultFunctionProps: {
    srcPath: "lambda/rest/functions/",
  },
  routes: {
    "GET /folders": "get-folders.main",
    "GET /global-search": "global-search.main",
    "GET /tags": "get-tags.main",
    "GET /trash": "get-deleted-items.main",
  },
});

Thanks for the feedback guys. The only reason hold us back adding a

basePath

field to the Function is we messed up the naming for

srcPath

.

srcPath

really meant “path to your package.json”, but ppl mis-use it as “base path”.

Ohh indeed the

package.json

is referenced under

FunctionProps

. I saw examples of relative paths scattered in the Function docs and sort of ran with it 😅

Yeah, it is a bit confusing rn. Will fix!