-
-
Notifications
You must be signed in to change notification settings - Fork 735
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
feat: add sdk example box #8092
Conversation
sjaanus
commented
Sep 5, 2024
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.OpenSSF Scorecard
Scanned Manifest Files |
...rc/component/project/Project/PaginatedProjectFeatureToggles/ProjectOnboarding/SdkExample.tsx
Outdated
Show resolved
Hide resolved
import { type SelectChangeEvent, styled, Typography } from '@mui/material'; | ||
import { Link } from 'react-router-dom'; | ||
import Select from '../../../../common/select'; | ||
import { OFFICIAL_SDKS } from '../../../../integrations/IntegrationList/AvailableIntegrations/SDKs'; |
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.
I added the SDK list (at the type level, we can add value level list too) in the onboarding directory. The file is called sharedTypes.ts. We can use the integrations dir but I wanted to control which ones we display in the onboarding just in case the lists don't match between integrations and onboarding.
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.
We have value level lists in the SelectSdk.tsx so you can export it from there. Then we don't depend on the other module.