-
Notifications
You must be signed in to change notification settings - Fork 186
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integration requests form #440
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
WalkthroughThe recent updates to the Changes
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? TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Additionally, you can add CodeRabbit Configration File (
|
There was a problem hiding this 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
Files selected for processing (1)
- .github/ISSUE_TEMPLATE/new-integration-request.yml (2 hunks)
Additional comments not posted (4)
.github/ISSUE_TEMPLATE/new-integration-request.yml (4)
3-3
: The title format is clear and specific, which is good for automatic issue labeling and sorting.
21-21
: The updated label "Category" aligns well with the new ID, enhancing clarity.
22-22
: Allowing multiple selections in the category dropdown enhances flexibility for the users.
26-41
: The updated options in the dropdown cover a broad range of software categories, which should enhance the form's utility.
@@ -15,16 +16,29 @@ body: | |||
validations: | |||
required: true | |||
- type: dropdown | |||
id: vertical | |||
id: software_category |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tip
Codebase Verification
Ensure that any scripts or automation that previously used id: vertical
are updated to accommodate the new id: software_category
. The search results indicate multiple occurrences of the term "vertical" across various files, including scripts, services, and documentation. These references need to be reviewed and updated accordingly.
packages/api/swagger/swagger-spec.json
packages/shared/src/providers.ts
packages/shared/src/utils.ts
packages/shared/src/envConfig.ts
packages/shared/src/authUrl.ts
packages/api/src/ticketing/user/sync/sync.service.ts
packages/api/scripts/oauthConnector.js
packages/api/scripts/commonObject.sh
packages/api/scripts/connectorUpdate.js
packages/api/src/crm/task/sync/sync.service.ts
packages/api/src/@core/field-mapping/field-mapping.service.ts
packages/api/src/@core/sync/sync.service.ts
packages/api/src/@core/passthrough/passthrough.service.ts
packages/api/src/@core/connections-strategies/connections-strategies.service.ts
docs/quick-start.mdx
docs/open-source/contributors.mdx
docs/glossary/connection-object.mdx
docs/core-concepts/embedded-catalog.mdx
docs/core-concepts/auth.mdx
INTEGRATIONS.md
apps/embedded-catalog/react/src/index.tsx
apps/client-ts/src/state/verticalStore.ts
apps/client-ts/src/hooks/useProviderProperties.tsx
apps/client-ts/src/components/Connection/ConnectionTable.tsx
apps/client-ts/src/components/Configuration/Connector/VerticalSelector.tsx
apps/client-ts/src/components/Configuration/Connector/ConnectorList.tsx
apps/client-ts/src/components/Configuration/Connector/ConnectorDisplay.tsx
apps/client-ts/src/components/Configuration/AddAuthCredentialsForm.tsx
apps/magic-link/src/hooks/useOAuth.ts
Analysis chain
Ensure that any scripts or automation that previously used id: vertical
are updated to accommodate the new id: software_category
.
Scripts Executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Search for occurrences of the old ID 'vertical' to ensure they are updated.
# Test: Search for the old ID usage. Expect: No occurrences of 'vertical'.
rg --type yaml $'id: vertical'
Length of output: 31
Script:
#!/bin/bash
# Description: Search for occurrences of the old ID 'vertical' in all file types to ensure they are updated.
# Test: Search for the old ID usage in all files. Expect: No occurrences of 'vertical'.
rg 'id: vertical'
Length of output: 19
Script:
#!/bin/bash
# Description: Search for occurrences of the old ID 'vertical' in scripts and documentation to ensure they are updated.
# Test: Search for the old ID usage in scripts and documentation. Expect: No occurrences of 'vertical'.
rg 'vertical'
Length of output: 50239
No description provided.