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

Add search (Autocomplete) in environment/group dropdown in create/import forms #1347

Merged
merged 10 commits into from
Jun 25, 2024

Conversation

dlpzx
Copy link
Contributor

@dlpzx dlpzx commented Jun 19, 2024

Feature or Bugfix

  • Feature

Detail

Autocomplete for environments and teams in the following frontend views as requested in 1012.

This PR introduces a 2 new Shared frontend components: EnvironmentTeamDropdown and EnvironmentTeamDatasetsDropdown. They are generic formik fields that can be reused in Formik forms in several modules. Some creation forms include custom parameters that are fetched alongside the environments and teams (e.g. Notebooks sets VPCs). For those cases, we implement the Autocomplete logic in the view itself

  • DashboardImportForm.js - using EnvironmentTeamDropdown
  • MLStudioCreateForm.js - using EnvironmentTeamDropdown
  • NotebookCreateForm.js - custom
  • OmicsRunCreateForm.js - using EnvironmentTeamDatasetsDropdown
  • DatasetCreateForm.js - custom
  • DatasetImportForm.js - custom

Pipelines in a separate PR

In all forms we use SamlAdminGroupName instead of SamlGroupName as a standard that allows us to use Shared components

Relates

Security

Please answer the questions below briefly where applicable, or write N/A. Based on
OWASP 10.

  • Does this PR introduce or modify any input fields or queries - this includes
    fetching data from storage outside the application (e.g. a database, an S3 bucket)?
    • Is the input sanitized?
    • What precautions are you taking before deserializing the data you consume?
    • Is injection prevented by parametrizing queries?
    • Have you ensured no eval or similar functions are used?
  • Does this PR introduce any functionality or component that requires authorization?
    • How have you ensured it respects the existing AuthN/AuthZ mechanisms?
    • Are you logging failed auth attempts?
  • Are you using or adding any cryptographic features?
    • Do you use a standard proven implementations?
    • Are the used keys controlled by the customer? Where are they stored?
  • Are you introducing any new policies/roles/users?
    • Have you used the least-privilege principle? How?

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@dlpzx dlpzx changed the title Feat/search env dropdown generic Add search (Autocomplete) in environment/group dropdown in create/import forms Jun 19, 2024
@dlpzx dlpzx force-pushed the feat/search-env-dropdown-generic branch from 95a8512 to 2298fa7 Compare June 21, 2024 13:14
Comment on lines +538 to +554
<TextField
error={Boolean(
touched.SamlAdminGroupName &&
errors.SamlAdminGroupName
)}
helperText={
touched.SamlAdminGroupName &&
errors.SamlAdminGroupName
}
fullWidth
disabled
label="Team"
value="No teams found for this environment"
variant="outlined"
/>
)}
</Box>
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: This TextField component (and all other ones for when groupOptions is empty) has a different sizing then the other TextFields on the form and the other TextField when groupOptions are present

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I noticed, not very sure why

Copy link
Contributor

@noah-paige noah-paige left a comment

Choose a reason for hiding this comment

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

lgtm - approving

@dlpzx dlpzx merged commit 194770c into main Jun 25, 2024
9 checks passed
@dlpzx dlpzx deleted the feat/search-env-dropdown-generic branch June 26, 2024 09:26
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.

None yet

2 participants