spaxel/dashboard/node_modules/xmlchars
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
..
xml feat: implement repeated-setting change detection with guided calibration 2026-04-11 00:18:19 -04:00
xmlns/1.0 feat: implement repeated-setting change detection with guided calibration 2026-04-11 00:18:19 -04:00
LICENSE 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
xmlchars.d.ts feat: implement repeated-setting change detection with guided calibration 2026-04-11 00:18:19 -04:00
xmlchars.js feat: implement repeated-setting change detection with guided calibration 2026-04-11 00:18:19 -04:00
xmlchars.js.map feat: implement repeated-setting change detection with guided calibration 2026-04-11 00:18:19 -04:00

Utilities for determining whether characters belong to character classes defined by the XML specs.

Organization

It used to be that the library was contained in a single file and you could just import/require/what-have-you the xmlchars module. However, that setup did not work well for people who cared about code optimization. Importing xmlchars meant importing all of the library and because of the way the code was generated there was no way to shake the resulting code tree.

Different modules cover different standards. At the time this documentation was last updated, we had:

  • xmlchars/xml/1.0/ed5 which covers XML 1.0 edition 5.
  • xmlchars/xml/1.0/ed4 which covers XML 1.0 edition 4.
  • xmlchars/xml/1.1/ed2 which covers XML 1.0 edition 2.
  • xmlchars/xmlns/1.0/ed3 which covers XML Namespaces 1.0 edition 3.

Features

The "things" each module contains can be categorized as follows:

  1. "Fragments": these are parts and pieces of regular expressions that correspond to the productions defined in the standard that the module covers. You'd use these to build regular expressions.

  2. Regular expressions that correspond to the productions defined in the standard that the module covers.

  3. Lists: these are arrays of characters that correspond to the productions.

  4. Functions that test code points to verify whether they fit a production.