- ✅ Ticket 1.1: Estructura Clean Architecture en backend - ✅ Ticket 1.2: Schemas Zod compartidos - ✅ Ticket 1.3: Refactorización drugs.ts (1362 → 8 archivos modulares) - ✅ Ticket 1.4: Refactorización procedures.ts (3583 → 6 archivos modulares) - ✅ Ticket 1.5: Eliminación de duplicidades (~50 líneas) Cambios principales: - Creada estructura Clean Architecture en backend/src/ - Schemas Zod compartidos en backend/src/shared/schemas/ - Refactorización modular de drugs y procedures - Utilidades genéricas en src/utils/ (filter, validation) - Eliminados scripts obsoletos y documentación antigua - Corregidos errores: QueryClient, import test-error-handling - Build verificado y funcionando correctamente |
||
|---|---|---|
| .. | ||
| index.js | ||
| LICENSE-MIT.txt | ||
| package.json | ||
| README.md | ||
is-potential-custom-element-name 
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
| Mathias Bynens |
License
is-potential-custom-element-name is available under the MIT license.