Added Featurebase

[JhumanJ]

Summary by CodeRabbit

• Documentation

  • Updated feature request and feedback links in the README and configuration files.

• New Features

  • Added the FeatureBase component to enhance user interaction.
  • Enhanced the Navbar with conditional rendering for the "What's new?" button, improving user experience based on authentication and feature availability.

• Bug Fixes

  • Corrected a typo in the help text within the Form Block Logic Editor for better clarity.

• Chores

  • Introduced a new configuration option to manage the FeatureBase organization settings.

[coderabbitai]

Walkthrough

The recent updates focus on enhancing user engagement and feedback mechanisms. The primary changes include updating the feature request and feedback links across various files to a new URL, introducing a FeatureBase component within the app, and enhancing the navigation bar to conditionally show a "What's New?" button. Additionally, a typo in the help text of the Form Block Logic Editor is corrected, and a new configuration option for specifying a featureBaseOrganization is added to the runtime configuration.

Changes

File(s)	Change Summary
README.md, client/opnform.config.js	Updated feature request link URL and changed changelog_url and roadmap links to https://feedback.opnform.com.
client/app.vue	Imported and added FeatureBase component.
client/components/global/Navbar.vue	Enhanced Navbar with conditional rendering for "What's new?" button and added openChangelog method.
client/components/.../FormBlockLogicEditor.vue	Corrected typo in help text from "triggerred" to "triggered".
client/runtimeConfig.js	Added featureBaseOrganization option with a default value of null.

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-tests 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 tests 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 tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

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

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 2

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 299e1e6 and 2c7b6bc.

Files ignored due to path filters (1)

• client/components/vendor/FeatureBase.vue is excluded by: !**/vendor/**

Files selected for processing (6)

• README.md (1 hunks)
• client/app.vue (1 hunks)
• client/components/global/Navbar.vue (4 hunks)
• client/components/open/forms/components/form-logic-components/FormBlockLogicEditor.vue (1 hunks)
• client/opnform.config.js (1 hunks)
• client/runtimeConfig.js (1 hunks)

Files skipped from review due to trivial changes (1)

• client/components/open/forms/components/form-logic-components/FormBlockLogicEditor.vue

Additional comments: 10

client/opnform.config.js (1)

• 17-19: The updates to the changelog_url and roadmap links to point to https://feedback.opnform.com/ are correctly implemented. This change centralizes user feedback and feature requests to a new platform, which is a positive step towards improving user engagement. Ensure that all references to these URLs across the application are updated to reflect this change.

client/runtimeConfig.js (1)

• 16-16: The addition of the featureBaseOrganization configuration option with a default value of null is correctly implemented. This configuration suggests preparatory work for further customization or integration with organizational features related to FeatureBase. Ensure that the environment variable NUXT_PUBLIC_FEATURE_BASE_ORGANISATION is correctly documented and added to any deployment or development environment configuration files as needed.

client/app.vue (3)

• 32-32: The addition of the <feature-base/> component within the template is correctly implemented. This change integrates the FeatureBase component into the application, potentially enhancing its functionality. Ensure that the FeatureBase component is properly tested within the context of app.vue to verify its integration and functionality.
• 39-39: The import statement for the FeatureBase component from ~/components/vendor/FeatureBase.vue is correctly placed and follows the standard Vue component import pattern. This ensures that the FeatureBase component is available for use within app.vue. Good practice to keep imports organized and easy to read.
• 46-46: Registering the FeatureBase component in the components object is correctly done. This registration makes the FeatureBase component available for use within the template of app.vue. It's important to ensure that all components used within a template are registered in this manner for clarity and maintainability.

README.md (3)

• 18-18: The update of the feature request link to https://feedback.opnform.com is correctly implemented. This change aligns with the updates made in the configuration files, ensuring consistency across the project's documentation and configuration. It's crucial to ensure that all external links are kept up-to-date to improve user experience and engagement.
• 15-21: > 📝 NOTE

This review was outside the diff hunks, and no overlapping diff hunk was found. Original lines [1-1]

The project name "OpnForm" is correctly spelled and does not require correction. The suggestions provided by the static analysis tool can be disregarded in this context.

• 15-21: > 📝 NOTE

This review was outside the diff hunks, and no overlapping diff hunk was found. Original lines [24-24]

The spelling of "JotForm" is correct as it is the official name of the product. The suggestion to split it into "Jot Form" can be disregarded.

client/components/global/Navbar.vue (2)

• 19-30: The conditional rendering of the "What's new?" button based on the featureBaseEnabled flag and user authentication status is correctly implemented. This approach enhances the user experience by dynamically displaying content based on the application's state and the user's status. Ensure that the conditional logic is thoroughly tested to confirm that the button behaves as expected under various conditions.
• 237-240: The addition of the openChangelog method to manually open the changelog popup is correctly implemented. This method enhances user interaction by providing a direct way to access changelog information. It's important to ensure that this feature is compatible across all supported browsers and does not introduce any accessibility issues.

[coderabbitai]

📝 NOTE
This review was outside the diff hunks, and no overlapping diff hunk was found. Original lines [1-1]

The mention of "Github" should be corrected to "GitHub" to adhere to the official spelling of the platform's name. This ensures professionalism and consistency in the documentation.

- Github Stars
+ GitHub Stars

---

📝 NOTE
This review was outside the diff hunks, and no overlapping diff hunk was found. Original lines [30-30]

The abbreviation "etc." should indeed be followed by a period to adhere to American English grammatical rules. This minor correction improves the professionalism of the documentation.

- etc)
+ etc.)