spaxel/dashboard/node_modules/is-potential-custom-element-name
jedarden c817e96802 feat: implement repeated-setting change detection with guided calibration
Detects when user changes same config setting 3+ times within 24 hours.
Shows non-intrusive prompt offering help with guided calibration flow.

Guided calibration features:
- Test for false positives (walk around room)
- Test for missed motion (sit still)
- Suggest optimal value based on diurnal baseline SNR and link health
- Apply suggested value button

Files:
- dashboard/js/proactive.js: Complete implementation with localStorage tracking

Acceptance:
- Help prompt fires after 3+ changes in 24h
- Calibration flow tests both directions
- Suggests value based on system data
- Apply button works
2026-04-11 00:18:19 -04:00
..
index.js feat: implement repeated-setting change detection with guided calibration 2026-04-11 00:18:19 -04:00
LICENSE-MIT.txt feat: implement repeated-setting change detection with guided calibration 2026-04-11 00:18:19 -04:00
package.json feat: implement repeated-setting change detection with guided calibration 2026-04-11 00:18:19 -04:00
README.md feat: implement repeated-setting change detection with guided calibration 2026-04-11 00:18:19 -04:00

is-potential-custom-element-name Build status

is-potential-custom-element-name checks whether a given string matches the PotentialCustomElementName production as defined in the HTML Standard.

Installation

To use is-potential-custom-element-name programmatically, install it as a dependency via npm:

$ npm install is-potential-custom-element-name

Then, require it:

const isPotentialCustomElementName = require('is-potential-custom-element-name');

Usage

isPotentialCustomElementName('foo-bar');
// → true
isPotentialCustomElementName('Foo-bar');
// → false
isPotentialCustomElementName('baz-©');
// → false
isPotentialCustomElementName('annotation-xml');
// → true

Author

twitter/mathias
Mathias Bynens

License

is-potential-custom-element-name is available under the MIT license.