Skip to content

feat(rfc): JSON embedded files#126

Open
crowecawcaw wants to merge 1 commit intoOpenJobDescription:mainlinefrom
crowecawcaw:rfc
Open

feat(rfc): JSON embedded files#126
crowecawcaw wants to merge 1 commit intoOpenJobDescription:mainlinefrom
crowecawcaw:rfc

Conversation

@crowecawcaw
Copy link
Copy Markdown
Contributor

Tracking Issue: #124

This is a request for comments about JSON embedded files.


By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Signed-off-by: Stephen Crowe <6042774+crowecawcaw@users.noreply.github.com>
@crowecawcaw crowecawcaw requested a review from a team as a code owner April 13, 2026 15:35
the template has been parsed. If the substituted value contains characters that break the
quoting chosen at serialization time, the worker gets a parse error.

This issue has caused real bugs:
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Totally agree this is a big problem!

data:
renderer: "{{Param.Renderer}}"
resolution: ["{{Param.Width}}", "{{Param.Height}}"]
passes:
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we define a limit to the max depth? Say 2?


The written file `init-data.json` would contain:

```json
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd like to know or think about if we add limits. EG: Max number of keys, max length of keys and values.

Thinking about pen test overflow like cases. If we define something reasonable it would be constraint.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants