easywebapp / web-utility Goto Github PK

https://github.com/EasyWebApp/web-utility/blob/master/source/parser.ts#L16

https://stackoverflow.com/questions/10631494/json-parse-parses-converts-big-numbers-incorrectly
https://www.irt.org/script/1031.htm

https://github.com/EasyWebApp/web-utility/blob/master/source/URL.ts#L13

In toCamelCase, I cann't convert to 'asa sasa' to 'asaSasa'
data.ts:32
maybe we can polish the pattern of the regExp

 return raw.replace(/^[a-z]|-[a-z]|\s+[a-z]/g, (match, offset)

In formToJSON, when there's only one radio or checkbox for a name(acting as a switch), and if that radio/checkbox is not checked, there would be no such field in the return json object.
So if user turn off a switch when updating a form, it would not work, the field would still be on.

MDN_scrollIntoView
API-Docs_scrollTo

• behavior Optional
  Defines the transition animation. One of auto or smooth. Defaults to auto.

• block Optional
  Defines vertical alignment. One of start, center, end, or nearest. Defaults to start.

• inline Optional
  Defines horizontal alignment. One of start, center, end, or nearest. Defaults to nearest.

In toHyphenCase, I cann't convert to 'socia media' to 'socia-media'
data.ts:32
maybe we can polish the pattern of the regExp

function toHyphenCase(raw:string) {
  return raw.replace(
      /[A-Z]+|[^A-Za-z][A-Za-z]/g,
      (match, offset) => `${offset ? '-' : ''}${(match[1]||match[0]).toLowerCase()}`
  );
}

When I use https://github.com/idea2app/REST-Node-ts npm install error message:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: @idea2app/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/typescript
npm ERR!   dev typescript@"~5.1.6" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer typescript@"^4.1.0" from [email protected]
npm ERR! node_modules/web-utility
npm ERR!   web-utility@"^4.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution