-
Notifications
You must be signed in to change notification settings - Fork 210
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
MNTOR-3396 - Organize storybook dashboard states #5308
Open
codemist
wants to merge
13
commits into
main
Choose a base branch
from
MNTOR-3395
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Commits on Nov 14, 2024
-
Migrate utils/hibp.js to TypeScript
This removes the `Breach` type in functions/universal/breaches, which was created when first introducing TypeScript and the flow of data was still unclear, but by now had overlap with other types and no clear provenance. Instead, there are now three breach-related types, that represent where the data came from: - HibpGetBreachesResponse: this is an array of breach elements as returned from the HIBP API, unprocessed. Properties are in PascalCase, so are a breach's data classes. - BreachRow: this is a breach's data as stored in our database, along with some data we added to it, such as a favicon URL. Properties are snake_case, and data classes are lowercased and kebab-cased by the formatDataClassesArray function. - HibpLikeDbBreach: this is a breach's data fetched from the database, but stored in an object meant to look like the ones in HibpGetBreachesResponse. In other words, it contains the same data as BreachRow (including lowercased, kebab-cased data classes), but on PascalCase properties. The latter is somewhat of a historical artefact, because we used to try to load breaches from our database, then if our database didn't contain any breaches yet, fetch them live from the HIBP API and continue working with that. We no longer do that: now, even after fetching them from the HIBP API, we do a new query to get them from the database and process them into HibpLikeDbBreach, so that we can assume a consisent data structure everywhere we work with breaches.
Configuration menu - View commit details
-
Copy full SHA for 3b4cb99 - Browse repository at this point
Copy the full SHA 3b4cb99View commit details -
Configuration menu - View commit details
-
Copy full SHA for 17557e6 - Browse repository at this point
Copy the full SHA 17557e6View commit details -
Configuration menu - View commit details
-
Copy full SHA for 2ad7025 - Browse repository at this point
Copy the full SHA 2ad7025View commit details -
Configuration menu - View commit details
-
Copy full SHA for 0202072 - Browse repository at this point
Copy the full SHA 0202072View commit details -
Configuration menu - View commit details
-
Copy full SHA for 652e7cc - Browse repository at this point
Copy the full SHA 652e7ccView commit details -
Configuration menu - View commit details
-
Copy full SHA for 678e63c - Browse repository at this point
Copy the full SHA 678e63cView commit details -
Configuration menu - View commit details
-
Copy full SHA for 5ff80f0 - Browse repository at this point
Copy the full SHA 5ff80f0View commit details -
Configuration menu - View commit details
-
Copy full SHA for 1e8a5ae - Browse repository at this point
Copy the full SHA 1e8a5aeView commit details -
Configuration menu - View commit details
-
Copy full SHA for 708434f - Browse repository at this point
Copy the full SHA 708434fView commit details -
Configuration menu - View commit details
-
Copy full SHA for a1185b1 - Browse repository at this point
Copy the full SHA a1185b1View commit details -
Configuration menu - View commit details
-
Copy full SHA for 2dece42 - Browse repository at this point
Copy the full SHA 2dece42View commit details -
Configuration menu - View commit details
-
Copy full SHA for a46ea36 - Browse repository at this point
Copy the full SHA a46ea36View commit details -
Configuration menu - View commit details
-
Copy full SHA for 21db932 - Browse repository at this point
Copy the full SHA 21db932View commit details
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.