feat: input schema defaults in getInput #409
Conversation
github-actions
bot
added
t-tooling
| return null; | ||
| } | ||
|
|
||
| export const readInputSchema = (): Dictionary | null => { |
There was a problem hiding this comment.
nit: can we make all of them (readJSONIfExists, readInputSchema, getDefaultsFromInputSchema) function (or make all of them const arrow function)?
|
|
||
| export const readInputSchema = (): Dictionary | null => { | ||
| const localConfig = readJSONIfExists( | ||
| join(process.cwd(), ACTOR_SPECIFICATION_FOLDER, LOCAL_CONFIG_NAME), |
There was a problem hiding this comment.
process.cwd() will likely break if the Dockerfile entry point is not npm (--prefix=app/) start, but e.g. node app/main.js
But I'm not sure how else we would refer to these files 🤔 I guess it's okay to live with this, especially since on Platform, we load this via API.
There was a problem hiding this comment.
I only gave it a quick look, but it looks like we don't copy the .actor directory in our Dockerfiles anyway, so for the "build a Docker image and run it outside of the platform" use case, the answer to "But I'm not sure how else we would refer to these files" is probably "tough luck lol" 🤷
But if we add a nice error log when there's not input schema to be found, yeah, we can live with that.
| .build(env.actorBuildId) | ||
| .get(); | ||
|
|
||
| inputSchema = buildData?.actorDefinition?.input; |
There was a problem hiding this comment.
I would at least log an error if this is not present in the response.
| inputSchema = buildData?.actorDefinition?.input; | ||
| } else { | ||
| // On local, we can get the input schema from the local config | ||
| inputSchema = readInputSchema(); |
There was a problem hiding this comment.
It'd also be nice to log something if no input schema is found.
|
|
||
| export const readInputSchema = (): Dictionary | null => { | ||
| const localConfig = readJSONIfExists( | ||
| join(process.cwd(), ACTOR_SPECIFICATION_FOLDER, LOCAL_CONFIG_NAME), |
There was a problem hiding this comment.
I only gave it a quick look, but it looks like we don't copy the .actor directory in our Dockerfiles anyway, so for the "build a Docker image and run it outside of the platform" use case, the answer to "But I'm not sure how else we would refer to these files" is probably "tough luck lol" 🤷
But if we add a nice error log when there's not input schema to be found, yeah, we can live with that.
Way too overdue, closes #287