Skip to content

Conversation

@jif-oai
Copy link
Collaborator

@jif-oai jif-oai commented Oct 28, 2025

The goal is to have a single place where we actually write files

In a follow-up PR, will move everything config related in a dedicated module and move the helpers in a dedicated file

@jif-oai jif-oai changed the title [WIP] chore: config editing cleaning Oct 28, 2025
@jif-oai
Copy link
Collaborator Author

jif-oai commented Oct 28, 2025

@codex review

@chatgpt-codex-connector
Copy link
Contributor

Codex Review: Didn't find any major issues. Already looking forward to the next diff.

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Copy link
Collaborator

@pakrym-oai pakrym-oai left a comment

Choose a reason for hiding this comment

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

Beautiful.

Three comments, neither blocking:

  1. Consider representing config update using a struct that mirrors Config struct. It becomes very clear what exactly is being updated and why.
  2. Let's assert before/after of config edits against raw strings to ensure formatting isn't messed up.
  3. Can pick either builder or edit array an use it consistently?
@jif-oai jif-oai enabled auto-merge (squash) October 29, 2025 18:20
@jif-oai jif-oai merged commit db31f69 into main Oct 29, 2025
61 of 67 checks passed
@jif-oai jif-oai deleted the jif/config-editing-refactor branch October 29, 2025 20:52
@github-actions github-actions bot locked and limited conversation to collaborators Oct 29, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

3 participants