🐛 If Column contains a null data then act as if the colum was set trrue fixes #561

[subin-chella]

#561

Summary by CodeRabbit

• New Features
  • Updated logic for the status property in the DynamicCatalog component, improving the handling of null values.
• Bug Fixes
  • Enhanced specificity in the status assignment, potentially resolving inconsistencies in rendering or behavior related to falsy values.

[rflihxyz]

Qovery can create a Preview Environment for this PR.
To trigger its creation, please post a comment with one of the following command.

Command	Blueprint environment
/qovery preview 783d0240-ec38-4387-a9a9-8e225f1bd3e1	dev
/qovery preview {all|UUID1,UUID2,...}	To preview multiple environments

---

This comment has been generated from Qovery AI 🤖.
Below, a word from its wisdom :

One day they will all understand

[changeset-bot]

⚠️ No Changeset found

Latest commit: 68dae36

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[coderabbitai]

Walkthrough

Walkthrough

The change modifies the logic for the status property in the DynamicCatalog component. It introduces a specific check for null values, setting status to "true" when value is null. For all other values, it retains the original conversion to a string. This alteration affects how the status property is defined, particularly influencing any components or functions that interact with it.

Changes

File	Change Summary
apps/.../PanoraDynamicCatalog.tsx	Updated logic for determining status property; added check for null values.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant DynamicCatalog
    participant Component

    User->>DynamicCatalog: Request data
    DynamicCatalog->>DynamicCatalog: Check value
    alt value is null
        DynamicCatalog->>DynamicCatalog: Set status = "true"
    else
        DynamicCatalog->>DynamicCatalog: Set status = String(value)
    end
    DynamicCatalog->>Component: Return status
    Component->>User: Display status

Loading

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

Commits

Files that changed from the base of the PR and between 66be9ac and 68dae36.

Files selected for processing (1)

• apps/embedded-catalog/react/src/components/PanoraDynamicCatalog.tsx (1 hunks)

Additional comments not posted (1)

apps/embedded-catalog/react/src/components/PanoraDynamicCatalog.tsx (1)

170-171: LGTM! The logic for handling null values is correct.

The change to treat null values as "true" for the status property aligns with the PR objective and ensures correct handling of null data.