Skip to content

Conversation

nornagon-openai
Copy link
Collaborator

all of my trust_level settings in my ~/.codex/config.toml were on one line.

- Avoid inline TOML tables for per-project entries
- Ensure explicit table headers for [projects] and each project key
- Add unit test to verify formatting (no inline tables)
Copy link
Collaborator

@dylan-hurd-oai dylan-hurd-oai left a comment

Choose a reason for hiding this comment

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

1 non-blocking comment about explicit-ness required. Thanks for fixing!

));
};
// Ensure we emit an explicit [projects] header
projects_tbl.set_implicit(false);
Copy link
Collaborator

Choose a reason for hiding this comment

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

Does toml require us to have [projects] to set [projects."/path/to/project"]? We parse [mcp_servers.playwright] and [profiles.oss] without [mcp_servers] or [profiles], respectively. Or is this just required to ensure the sub-tables are not in-line?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

hm yeah it's probably not required.

@nornagon-openai nornagon-openai merged commit 750ca9e into main Aug 21, 2025
15 checks passed
@nornagon-openai nornagon-openai deleted the chore/core-pretty-project-toml branch August 21, 2025 20:20
@github-actions github-actions bot locked and limited conversation to collaborators Aug 21, 2025
// Run the function; it should convert to explicit tables and set trusted
set_project_trusted(codex_home.path(), project_dir.path())?;

let contents = std::fs::read_to_string(&config_path)?;
Copy link
Collaborator

Choose a reason for hiding this comment

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

Is there a reason why we cannot assert_eq!() on contents? What is variable in this point of the test?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants