-
Notifications
You must be signed in to change notification settings - Fork 97
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
stats.ts
: count correctly the number keys remaining to be mapped
#2544
stats.ts
: count correctly the number keys remaining to be mapped
#2544
Conversation
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.
LGTM 🚢
scripts/stats.ts
Outdated
const doneKeys = Object.values(features).flatMap( | ||
(f) => f.compat_features ?? [], | ||
const doneKeys = Array.from( | ||
new Set(Object.values(features).flatMap((f) => f.compat_features ?? [])), | ||
); | ||
const toDoKeys = []; | ||
const deprecatedNonStandardKeys = []; |
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.
Is deprecatedNonStandardKeys
used at all still then?
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 removed unused vars with 5331aaf.
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.
Nice! 🚢
Now that we're adding discouraged features, we shouldn't exclude those keys from the count. This correctly measures the total keys remaining (with
currentBurndownSize
continuing to represent standard, non-deprecated keys).I've also future proofed the count, in the case of allowing a key to appear in multiple features.