- ✅ 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
41 lines
1.3 KiB
Markdown
41 lines
1.3 KiB
Markdown
# is-potential-custom-element-name [](https://travis-ci.org/mathiasbynens/is-potential-custom-element-name)
|
|
|
|
_is-potential-custom-element-name_ checks whether a given string matches [the `PotentialCustomElementName` production](https://html.spec.whatwg.org/multipage/scripting.html#prod-potentialcustomelementname) as defined in the HTML Standard.
|
|
|
|
## Installation
|
|
|
|
To use _is-potential-custom-element-name_ programmatically, install it as a dependency via [npm](https://www.npmjs.com/):
|
|
|
|
```bash
|
|
$ npm install is-potential-custom-element-name
|
|
```
|
|
|
|
Then, `require` it:
|
|
|
|
```js
|
|
const isPotentialCustomElementName = require('is-potential-custom-element-name');
|
|
```
|
|
|
|
## Usage
|
|
|
|
```js
|
|
isPotentialCustomElementName('foo-bar');
|
|
// → true
|
|
isPotentialCustomElementName('Foo-bar');
|
|
// → false
|
|
isPotentialCustomElementName('baz-©');
|
|
// → false
|
|
isPotentialCustomElementName('annotation-xml');
|
|
// → true
|
|
```
|
|
|
|
## Author
|
|
|
|
| [](https://twitter.com/mathias "Follow @mathias on Twitter") |
|
|
|---|
|
|
| [Mathias Bynens](https://mathiasbynens.be/) |
|
|
|
|
## License
|
|
|
|
_is-potential-custom-element-name_ is available under the [MIT](https://mths.be/mit) license.
|