Skip to content
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(webapp): Show integration issues in their settings #3044

Conversation

nalanj
Copy link
Contributor

@nalanj nalanj commented Nov 22, 2024

Waiting on #3050

Shows missing field errors on the integrations page and highlights the errors on the tab:

image

And in the integrations list:

image

https://linear.app/nango/issue/NAN-2168/surface-integrationsconnections-errors-in-nango-ui

  • Set up a new integration that needs configuration, but don't configure it
  • View the integration page. You should see a yellow dot in the settings tab and a banner saying what fields need to be configured

Copy link

linear bot commented Nov 22, 2024

@nalanj nalanj changed the title Alan/nan 2168 surface integrationsconnections errors in nango UI/integration validation show UI feat(webapp): Show integration issues in their settings Nov 22, 2024
@nalanj nalanj self-assigned this Nov 22, 2024
nalanj and others added 20 commits November 22, 2024 12:08
…68-surface-integrationsconnections-errors-in-nango-ui/integration-validation-show-ui
…ons-errors-in-nango-ui/integration-validation-show-ui
Copy link

gitguardian bot commented Nov 27, 2024

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
8205899 Triggered Generic Password 6175ebe packages/database/lib/getDbConfig.ts View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

…ons-errors-in-nango-ui/integration-validation-show-ui
@nalanj nalanj marked this pull request as ready for review November 27, 2024 16:43
@nalanj nalanj requested a review from a team November 27, 2024 16:44
Copy link
Collaborator

@TBonnin TBonnin left a comment

Choose a reason for hiding this comment

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

I would try to simplify all those switches but looks good otherwise

@nalanj nalanj merged commit 1445793 into master Nov 27, 2024
20 checks passed
@nalanj nalanj deleted the alan/nan-2168-surface-integrationsconnections-errors-in-nango-ui/integration-validation-show-ui branch November 27, 2024 20:32
if (!mappings) return null;

return integration.missing_fields.map((field) => mappings[field] || field).join(', ');
}
Copy link
Collaborator

Choose a reason for hiding this comment

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

Might have been more user friendly to display a global message and a message near each fields instead

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