1.18 ports7

[arkadius]

Describe your changes

Checklist before merge

• [ ] Related issue ID is placed at the beginning of PR title in [brackets] (can be GH issue or Nu Jira issue)
• [ ] Code is cleaned from temporary changes and commented out lines
• [ ] Parts of the code that are not easy to understand are documented in the code
• [ ] Changes are covered by automated tests
• [ ] Showcase in dev-application.conf added to demonstrate the feature
• [ ] Documentation added or updated
• [ ] Added entry in Changelog.md describing the change from the perspective of a public distribution user
• [ ] Added MigrationGuide.md entry in the appropriate subcategory if introducing a breaking change
• [ ] Verify that PR will be squashed during merge

Summary by CodeRabbit

Release Notes

• New Features

  • Enhanced validation feedback with loading indicators in the editor components.
  • Introduced a custom hook for managing Enter key actions based on specific conditions.

• Improvements

  • Updated components to allow for richer content rendering by accepting complex React elements.
  • Improved loading indicators and user interactions in the ScenarioLabels and UserDefinedListInput components.

• Documentation

  • Updated changelog and migration guide to reflect recent changes and enhancements.
  • Clarified content in the SpEL documentation for better readability and understanding.

[coderabbitai[bot]]

📝 Walkthrough

## Walkthrough The pull request introduces several modifications across various components in the Nussknacker application, primarily focusing on enhancing type flexibility and improving user interaction. The `EditableEditor` component's `validationLabelInfo` property type has been updated from `string` to `ReactNode`, allowing for more complex React elements. This change is reflected in the `Editor` component, where the `expressionInfo` property is similarly updated. Additionally, the `UserDefinedListInput` component has been enhanced to utilize a `useRef` hook for managing the AceEditor instance and incorporates a `CircularProgress` component to indicate loading states during user input. The `ScenarioLabels` component also sees improvements with the addition of a loading indicator and optimizations through the `useCallback` hook. A new custom hook, `useDelayedEnterAction`, has been introduced to manage actions triggered by the Enter key based on specific conditions. Overall, these changes reflect a concerted effort to improve the handling of validation information, user feedback during input, and the overall structure and type definitions within the components. ## Possibly related PRs - **#7124**: The changes in the main PR regarding the `validationLabelInfo` prop type update from `string` to `ReactNode` are related to the changes in the `Editor.ts` file where the `expressionInfo` prop type is also updated from `string` to `ReactNode`, indicating a consistent approach to handling validation information across components. - **#7159**: The modifications in the main PR that enhance the `EditableEditor` component's handling of validation information are relevant to the changes in the `Editor.ts` file, where the `expressionInfo` prop is similarly updated to allow for more complex React elements, suggesting a direct relationship in how validation information is processed in both components. - **#7162**: The changes in the main PR that involve the `EditableEditor` and `Editor` components are related to the introduction of the `useDelayedEnterAction` hook in the `UserDefinedListInput.tsx`, which also aims to improve user interaction and validation handling, indicating a broader effort to enhance input handling across components. - **#7174**: The main PR's updates to the `EditableEditor` and `Editor` components to support more complex validation information are connected to the changes in the `TemplateEvaluationResult` class, which is introduced in the context of rendering templates and validation, highlighting a cohesive approach to managing validation across the application. - **#7215**: The changes in the main PR that modify the `validationLabelInfo` prop to support `ReactNode` are relevant to the updates in the `EditableEditor` and `Editor` components, which also focus on enhancing the rendering of validation information, indicating a consistent strategy for validation across different components. - **#7216**: The adjustments made in the main PR to improve the handling of validation information in the `EditableEditor` component are related to the documentation changes in `Spel.md`, which clarify the conversion processes and types, ensuring that users understand how to effectively utilize these components in conjunction with SpEL. ## Suggested labels `docs`, `ui`, `client`

---

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](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

🪧 Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit , 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 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](https://docs.coderabbit.ai/guides/configure-coderabbit) 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](https://docs.coderabbit.ai) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

[github-actions[bot]]

created: #7222 :warning: Be careful! Snapshot changes are not necessarily the cause of the error. Check the logs.