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.

Sign up for GitHub

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

[HS-1262665] Fix addresses with zip codes not showing predictions #1233

Merged
merged 1 commit into from
Dec 19, 2024
Merged

[HS-1262665] Fix addresses with zip codes not showing predictions #1233

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions ...ntacts/ContactDetails/ContactDetailsTab/Mailing/StreetAutocomplete/StreetAutocomplete.tsx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -169,6 +169,9 @@
typeof option === 'string' ? option : option.description
}
options={predictions}
// Disable filtering addresses by the input and rely on the Google Maps API to provide
// relevant address predictions
filterOptions={(options) => options}

Check warning on line 174 in src/components/Contacts/ContactDetails/ContactDetailsTab/Mailing/StreetAutocomplete/StreetAutocomplete.tsx

View check run for this annotation

CodeScene Delta Analysis / CodeScene Cloud Delta Analysis (main)

❌ Getting worse: Complex Method 

StreetAutocomplete:React.FC<StreetAutocompleteProps> already has high cyclomatic complexity, and now it increases in Lines of Code from 120 to 121. This function has many conditional statements (e.g. if, for, while), leading to lower code health. Avoid adding more conditionals and code to it without refactoring.
value={streetValue}
onChange={(_event, newValue) => {
if (typeof newValue === 'string') {
Expand Down
Loading