Skip to content

fix: Non-printable character box missing when editing Cloud Config parameter#3218

Merged
mtrezza merged 1 commit intoparse-community:alphafrom
mtrezza:fix/info-box-cc-missing
Feb 13, 2026
Merged

fix: Non-printable character box missing when editing Cloud Config parameter#3218
mtrezza merged 1 commit intoparse-community:alphafrom
mtrezza:fix/info-box-cc-missing

Conversation

@mtrezza
Copy link
Member

@mtrezza mtrezza commented Feb 13, 2026

Pull Request

Issue

Non-printable character box not visible when editing Cloud Config parameter.

Summary by CodeRabbit

  • Bug Fixes

    • Improved detection and handling of non-printable characters in JSON configuration editors.
  • Style

    • Adjusted spacing in the information container for better visual alignment.

@parse-github-assistant
Copy link

parse-github-assistant bot commented Feb 13, 2026

🚀 Thanks for opening this pull request!

@parseplatformorg
Copy link
Contributor

Snyk checks have passed. No issues have been found so far.

Status Scanner Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@coderabbitai
Copy link

coderabbitai bot commented Feb 13, 2026

📝 Walkthrough

Walkthrough

JsonEditor components for Object and Array editors in the configuration dialog are now wrapped with NonPrintableHighlighter to handle non-printable content detection. Additionally, vertical spacing above the information badge in the highlighter component is adjusted from 8px to -4px.

Changes

Cohort / File(s) Summary
NonPrintableHighlighter styling and ConfigDialog integration
src/components/NonPrintableHighlighter/NonPrintableHighlighter.scss, src/dashboard/Data/Config/ConfigDialog.react.js
NonPrintableHighlighter wrapper applied to Object and Array JsonEditor components with isJson={true} and detectNonAlphanumeric={true} props. Info container margin-top adjusted from 8px to -4px for better visual alignment.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

🚥 Pre-merge checks | ✅ 3 | ❌ 1
❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Description check ⚠️ Warning The description is incomplete. It includes the Issue section but lacks the Approach section describing the actual changes and does not address the Tasks section. Add an Approach section explaining how the NonPrintableHighlighter was integrated into the JsonEditor components, and indicate whether tests or documentation updates were completed.
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the main change: fixing the missing non-printable character highlighter box in the Cloud Config parameter editor.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection ✅ Passed ✅ No merge conflicts detected when merging into alpha

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

No actionable comments were generated in the recent review. 🎉

🧹 Recent nitpick comments
src/components/NonPrintableHighlighter/NonPrintableHighlighter.scss (1)

107-109: Negative margin may clip or overlap content depending on parent context.

The margin-top: -4px pulls the info badge upward, which works for the Config dialog's JsonEditor layout but could cause visual overlap if NonPrintableHighlighter is reused in contexts with tighter spacing or overflow: hidden on a parent. Consider whether a context-specific override (e.g., a prop-driven class) would be safer than changing the shared style.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@mtrezza mtrezza changed the title fix: Non-printable character box not visible when editing Cloud Config parameter fix: Non-printable character box missing when editing Cloud Config parameter Feb 13, 2026
@mtrezza mtrezza merged commit 719ac09 into parse-community:alpha Feb 13, 2026
11 checks passed
@mtrezza mtrezza deleted the fix/info-box-cc-missing branch February 13, 2026 17:07
parseplatformorg pushed a commit that referenced this pull request Feb 13, 2026
# [9.0.0-alpha.2](9.0.0-alpha.1...9.0.0-alpha.2) (2026-02-13)

### Bug Fixes

* Non-printable character box missing when editing Cloud Config parameter ([#3218](#3218)) ([719ac09](719ac09))
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 9.0.0-alpha.2

@parseplatformorg parseplatformorg added the state:released-alpha Released as alpha version label Feb 13, 2026
parseplatformorg pushed a commit that referenced this pull request Feb 19, 2026
# [9.0.0](8.5.0...9.0.0) (2026-02-19)

### Bug Fixes

* Cloud Config parameter modal overlays non-printable character info box ([#3221](#3221)) ([983253e](983253e))
* Incomplete authentication on AI Agent endpoint ([GHSA-qwc3-h9mg-4582](GHSA-qwc3-h9mg-4582)) ([#3224](#3224)) ([f92a9ef](f92a9ef))
* Non-printable character box missing when editing Cloud Config parameter ([#3218](#3218)) ([719ac09](719ac09))

### Features

* Add option to block saving Cloud Config parameter if validation fails ([#3225](#3225)) ([41691aa](41691aa))
* Add Regex string validation when editing Cloud Config parameter ([#3222](#3222)) ([067b9d1](067b9d1))
* Add support for checkbox, toggle, text input elements to script form ([#3219](#3219)) ([b9366bc](b9366bc))
* Add support for reversing info panel auto-scroll direction while holding Command+Option keys ([#3220](#3220)) ([7ebd121](7ebd121))
* Remove Node 18 support ([#3212](#3212)) ([a5c1bb2](a5c1bb2))

### BREAKING CHANGES

* Removes support for Node 18. ([a5c1bb2](a5c1bb2))
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 9.0.0

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

Labels

state:released Released as stable version state:released-alpha Released as alpha version

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants