Skip to content

Feature/config endpoint updates#5

Merged
shuv1337 merged 13 commits intoconfig-api-improvementsfrom
feature/config-endpoint-updates
Nov 7, 2025
Merged

Feature/config endpoint updates#5
shuv1337 merged 13 commits intoconfig-api-improvementsfrom
feature/config-endpoint-updates

Conversation

@shuv1337
Copy link
Copy Markdown
Collaborator

@shuv1337 shuv1337 commented Nov 6, 2025

No description provided.

shuv1337 and others added 8 commits November 6, 2025 12:14
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
[WIP] Address feedback on the /config endpoint update PR
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to 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 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +897 to +900
// Check write permissions
try {
await fs.access(Global.Path.config, fs.constants.W_OK)
} catch (err) {
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Fix permission check using fs.promises constants

When updating the global config the code checks write permission via await fs.access(Global.Path.config, fs.constants.W_OK), but fs here is imported from fs/promises and does not expose a constants property. That call throws a TypeError before the permission check happens, so every global config update will fail regardless of actual permissions. Import constants from fs (or use import * as fs from 'fs' for the constants) before calling access.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

@codex apply the fix

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

@copilot apply the fix

Copy link
Copy Markdown

Copilot AI commented Nov 6, 2025

@kcrommett I've opened a new pull request, #6, to work on those changes. Once the pull request is ready, I'll request review from you.

Copilot AI and others added 4 commits November 7, 2025 00:04
Co-authored-by: kcrommett <523952+kcrommett@users.noreply.github.com>
Co-authored-by: kcrommett <523952+kcrommett@users.noreply.github.com>
Fix fs.constants import in global config permission check
@shuv1337 shuv1337 changed the base branch from dev to config-api-improvements November 7, 2025 00:47
@shuv1337 shuv1337 merged this pull request into config-api-improvements Nov 7, 2025
2 of 4 checks passed
@shuv1337 shuv1337 deleted the feature/config-endpoint-updates branch November 21, 2025 00:33
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