-
-
Notifications
You must be signed in to change notification settings - Fork 330
fix: replace manual anomalies with a hampel filter #1997
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
Open
matthewp
wants to merge
6
commits into
npmx-dev:main
Choose a base branch
from
matthewp:feat/hampel-anomaly-detection
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.
+221
−452
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
a29c7d3
Replace manual anomalies with a hampel filter
matthewp 9cf5d8b
Fix typechecking
matthewp 55388db
Remove i18n keys
matthewp 7dc8c0b
Fix false positives for boundary points and low-volume packages
matthewp 88334f4
Add tweakable Hampel filter sliders to chart UI
matthewp bfc1bcb
[autofix.ci] apply automated fixes
autofix-ci[bot] File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
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.
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.
🧩 Analysis chain
🏁 Script executed:
Repository: npmx-dev/npmx.dev
Length of output: 93
🌐 Web query:
VueUse useLocalStorage mergeDefaults shallow merge documentation💡 Result:
In VueUse,
useLocalStorage()uses the same options asuseStorage(), and themergeDefaultsbehavior is documented on theuseStoragepage. (vueuse.org)mergeDefaults: truemerges the default value with the value read from storage, and for objects it does a shallow merge (top-level keys only). (vueuse.org)mergeDefaults(the docs explicitly show this pattern). (vueuse.org)Example (custom merge = deep merge):
Citations:
🏁 Script executed:
Repository: npmx-dev/npmx.dev
Length of output: 7350
🏁 Script executed:
Repository: npmx-dev/npmx.dev
Length of output: 43
🏁 Script executed:
Repository: npmx-dev/npmx.dev
Length of output: 236
🏁 Script executed:
Repository: npmx-dev/npmx.dev
Length of output: 2609
🏁 Script executed:
Repository: npmx-dev/npmx.dev
Length of output: 88
🏁 Script executed:
Repository: npmx-dev/npmx.dev
Length of output: 88
🏁 Script executed:
Repository: npmx-dev/npmx.dev
Length of output: 1232
🏁 Script executed:
Repository: npmx-dev/npmx.dev
Length of output: 885
Deep-merge nested
chartFiltersettings on hydration.VueUse's
useLocalStoragewithmergeDefaults: trueonly performs a shallow merge at the top level. Returning users with an existing storedchartFilterobject will not receive the newhampelWindowandhampelThresholdfields—the entire defaultchartFilteris replaced, leaving the new settings unset until explicitly written. VueUse documentation recommends a custom merge function for nested defaults.Suggested fix
if (!settingsRef) { settingsRef = useLocalStorage<AppSettings>(STORAGE_KEY, DEFAULT_SETTINGS, { - mergeDefaults: true, + mergeDefaults: (storageValue, defaults) => ({ + ...defaults, + ...storageValue, + connector: { ...defaults.connector, ...(storageValue.connector ?? {}) }, + sidebar: { ...defaults.sidebar, ...(storageValue.sidebar ?? {}) }, + chartFilter: { + ...defaults.chartFilter, + ...(storageValue.chartFilter ?? {}), + }, + }), }) }