
Research
Security News
Malicious PyPI Package Exploits Deezer API for Coordinated Music Piracy
Socket researchers uncovered a malicious PyPI package exploiting Deezer’s API to enable coordinated music piracy through API abuse and C2 server control.
@frui.ts/dirtycheck
Advanced tools
@frui.ts/dirtycheck
Dirty checking is based on the idea that the dirty flag of a particular property of an entity can be handled as a computed value comparing the current value of the property with the value at the time of dirty check initialization. Dirty watcher is thus just a factory that can generate such computed properties.
This feature is usually used to indicate which UI fields have been changed during the current session and have not been saved yet.
A dirty checker not only maintains information about whether an entity is dirty but also if the dirty flag should be displayed to the user (the isDirtyFlagVisible
property). For example, you don't want to display dirty flags when creating a new entity. You can set the isDirtyFlagVisible
property when instantiating / attaching a watcher or anytime later. The visibility is also turned on when checkDirtyChanges()
is called for the first time.
Dirty watcher that automatically observes the target entity and handles respective dirty flags.
// direct usage
const target = { firstName: "John" };
const watcher = new AutomaticDirtyWatcher(target, false);
let isTargetDirty = watcher.isDirty; // false
let isPropertyDirty = watcher.dirtyProperties.firstName; // false
target.firstName = "Jane";
isTargetDirty = watcher.isDirty; // true
isPropertyDirty = watcher.dirtyProperties.firstName; // true
watcher.reset();
isTargetDirty = watcher.isDirty; // false
isPropertyDirty = watcher.dirtyProperties.firstName; // false
// with helpers
import {
attachAutomaticDirtyWatcher,
isDirty,
hasVisibleDirtyChanges,
checkDirtyChanges,
resetDirty
} from "@frui.ts/dirtycheck";
const target = { firstName: "John" };
attachAutomaticDirtyWatcher(target);
// you can also use:
// const target = attachAutomaticDirtyWatcher({ firstName: "John" });
let dirty = isDirty(target); // false
dirty = isDirty(target, "firstName"); // false
let dirtyDisplayed = hasVisibleDirtyChanges(target); // false
target.firstName = "Jane";
dirty = isDirty(target); // true
dirty = isDirty(target, "firstName"); // true
dirtyDisplayed = hasVisibleDirtyChanges(target); // false!! - the entity is dirty but it is not indicated yet (e.g., UI for new entities)
dirty = checkDirtyChanges(target); // true - sets isDirtyFlagVisible to true and returns isDirty value
dirtyDisplayed = hasVisibleDirtyChanges(target); // true
resetDirty(target);
dirty = isDirty(target); // false
dirty = isDirty(target, "firstName"); // false
dirtyDisplayed = hasVisibleDirtyChanges(target); // false
Implements the interface IDirtyWatcher
, but you have to set dirty flags on properties manually.
// direct usage
const target = { firstName: "John" };
const watcher = new ManualDirtyWatcher(false);
watcher.setDirty("firstName");
let isTargetDirty = watcher.isDirty; // true
let isPropertyDirty = watcher.dirtyProperties.firstName; // true
watcher.reset();
isTargetDirty = watcher.isDirty; // false
isPropertyDirty = watcher.dirtyProperties.firstName; // false
// with helpers
import {
attachManualDirtyWatcher,
isDirty,
hasVisibleDirtyChanges,
setDirty,
checkDirtyChanges,
resetDirty
} from "@frui.ts/dirtycheck";
const target = { firstName: "John" };
attachManualDirtyWatcher(target);
// you can also use:
// const target = attachManualDirtyWatcher({ firstName: "John" });
let dirty = isDirty(target); // false
dirty = isDirty(target, "firstName"); // false
let dirtyDisplayed = hasVisibleDirtyChanges(target); // false
setDirty(target, target, "firstName");
dirty = isDirty(target); // true
dirty = isDirty(target, "firstName"); // true
dirtyDisplayed = hasVisibleDirtyChanges(target); // false!! - the entity is dirty but we don't want to indicate that (e.g., UI for new entities)
dirty = checkDirtyChanges(target); // true - it enables the visibility of dirty changes and returns isDirty value
dirtyDisplayed = hasVisibleDirtyChanges(target); // true
resetDirty(target);
dirty = isDirty(target); // false
dirty = isDirty(target, "firstName"); // false
dirtyDisplayed = hasVisibleDirtyChanges(target); // false
FAQs
Observable dirty checking
The npm package @frui.ts/dirtycheck receives a total of 259 weekly downloads. As such, @frui.ts/dirtycheck popularity was classified as not popular.
We found that @frui.ts/dirtycheck demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 5 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket researchers uncovered a malicious PyPI package exploiting Deezer’s API to enable coordinated music piracy through API abuse and C2 server control.
Research
The Socket Research Team discovered a malicious npm package, '@ton-wallet/create', stealing cryptocurrency wallet keys from developers and users in the TON ecosystem.
Security News
Newly introduced telemetry in devenv 1.4 sparked a backlash over privacy concerns, leading to the removal of its AI-powered feature after strong community pushback.