Skip to content

Conversation

@SangeetaMishr
Copy link
Collaborator

@SangeetaMishr SangeetaMishr commented Apr 29, 2025

added the description of skip validation

Summary by CodeRabbit

  • Documentation
    • Added a description for the new "Skip Validation" option on the Flow Listing Page, explaining how it allows users to bypass validation for dynamically generated results not pre-defined in the flow.

added the description of skip validation
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Apr 29, 2025

Walkthrough

A new section describing the "Skip Validation" feature was added to the Flow Listing Page Buttons documentation. This update explains an option that allows users to bypass validation when sending dynamically generated results that are not pre-defined in the flow, particularly when using the resume Flow API. No changes were made to code or public API declarations.

Changes

File(s) Change Summary
docs/3. Product Features/03. Flows/1. Flow Overview.md Added documentation for the "Skip Validation" feature under the Edit section of Flow Listing Page Buttons

Poem

A checkbox new, a path unbarred,
Skip validation—no result is marred.
For flows that flex and fields anew,
The docs now tell what you can do.
So onward flows, without a block,
The rabbit cheers—tick-tock, tick-tock! 🐇✨


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
🪧 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>, please review it.
    • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @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 using 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 generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

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.

@github-actions
Copy link

github-actions bot commented Apr 29, 2025

@github-actions github-actions bot temporarily deployed to pull request April 29, 2025 07:15 Inactive
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (1)
docs/3. Product Features/03. Flows/1. Flow Overview.md (1)

36-38: Correct indentation for list and description
The list item and its subsequent description should be indented consistently (4 spaces for nested list items) to satisfy Markdownlint MD005 and ensure proper rendering.

-   - **Skip Validation**: Check this box while sending results that are generated dynamically (not pre-defined in the flow). 
-This is helpful while using the [resume Flow API](https://api.glific.com/#89f5f6e6-9bdc-48c2-96c5-ad8c1f7a834b) and the flow doesn’t already have those results set up. It lets the flow continue without checking if those result fields were expected.
+    - **Skip Validation**: Check this box while sending results that are generated dynamically (not pre-defined in the flow). 
+      This is helpful while using the [resume Flow API](https://api.glific.com/#89f5f6e6-9bdc-48c2-96c5-ad8c1f7a834b) and the flow doesn’t already have those results set up. It lets the flow continue without checking if those result fields were expected.
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

36-36: Inconsistent indentation for list items at the same level
Expected: 4; Actual: 3

(MD005, list-indent)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5e50a00 and ad7867e.

📒 Files selected for processing (1)
  • docs/3. Product Features/03. Flows/1. Flow Overview.md (1 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
docs/3. Product Features/03. Flows/1. Flow Overview.md

36-36: Inconsistent indentation for list items at the same level
Expected: 4; Actual: 3

(MD005, list-indent)

corrected the typo error
Copy link
Member

@shijithkjayan shijithkjayan left a comment

Choose a reason for hiding this comment

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

LGTM

@github-actions github-actions bot temporarily deployed to pull request April 29, 2025 07:21 Inactive
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ad7867e and 6664b2b.

📒 Files selected for processing (1)
  • docs/3. Product Features/03. Flows/1. Flow Overview.md (1 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
docs/3. Product Features/03. Flows/1. Flow Overview.md

36-36: Inconsistent indentation for list items at the same level
Expected: 4; Actual: 3

(MD005, list-indent)

⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: Test deployment
  • GitHub Check: build

Comment on lines +36 to +38
- **Skip Validation** : Check this box while sending results that are generated dynamically (not pre-defined in the flow).
This is helpful while using the [resume Flow API](https://api.glific.com/#89f5f6e6-9bdc-48c2-96c5-ad8c1f7a834b) and the flow doesn’t already have those results set up.
It lets the flow continue without checking if those result fields were expected.
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Normalize indentation for the new "Skip Validation" bullet
The new bullet is currently indented with only 3 spaces and its description line starts with an extra leading space, breaking the list structure under Edit. Please align it with the other items:

-   - **Skip Validation** : Check this box while sending results that are generated dynamically (not pre-defined in the flow).
- This is helpful while using the [resume Flow API](https://api.glific.com/#89f5f6e6-9bdc-48c2-96c5-ad8c1f7a834b) and the flow doesn’t already have those results set up. 
+    - **Skip Validation** : Check this box while sending results that are generated dynamically (not pre-defined in the flow).
+This is helpful while using the [resume Flow API](https://api.glific.com/#89f5f6e6-9bdc-48c2-96c5-ad8c1f7a834b) and the flow doesn’t already have those results set up. 

This will satisfy the MD005 rule for consistent list indentation and remove unintended whitespace.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- **Skip Validation** : Check this box while sending results that are generated dynamically (not pre-defined in the flow).
This is helpful while using the [resume Flow API](https://api.glific.com/#89f5f6e6-9bdc-48c2-96c5-ad8c1f7a834b) and the flow doesn’t already have those results set up.
It lets the flow continue without checking if those result fields were expected.
- **Skip Validation** : Check this box while sending results that are generated dynamically (not pre-defined in the flow).
This is helpful while using the [resume Flow API](https://api.glific.com/#89f5f6e6-9bdc-48c2-96c5-ad8c1f7a834b) and the flow doesn’t already have those results set up.
It lets the flow continue without checking if those result fields were expected.
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

36-36: Inconsistent indentation for list items at the same level
Expected: 4; Actual: 3

(MD005, list-indent)

@shijithkjayan shijithkjayan merged commit b62e750 into main Apr 29, 2025
6 checks passed
@shijithkjayan shijithkjayan deleted the Updates_Flow-Overview.md branch April 29, 2025 08:25
@SangeetaMishr SangeetaMishr mentioned this pull request Apr 29, 2025
@coderabbitai coderabbitai bot mentioned this pull request Jul 30, 2025
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.

3 participants