Files
n8n_Demo/web_frontend/food-order-demo/node_modules/decode-named-character-reference/index.dom.js
Yep_Q c3eb7125cc feat: 创建食品订单班演示系统基础框架
详细说明:
- 基于文旅订单班框架复制创建food-order-demo项目
- 修改端口配置为4174避免冲突
- 更新LandingPage为青莳轻食主题(绿色健康风格)
- 重新定义7个食品行业专业Agent:
  * 市场研究专家:轻食市场分析、客群画像
  * 营养配方师:营养成分配比、低卡高蛋白设计
  * 供应链管理专家:有机食材供应、溯源体系
  * 品牌策划师:品牌定位、店铺空间布局
  * 财务分析师:投资预算、ROI分析
  * 运营管理专家:运营流程、品控标准
  * 食品创业导师:中央协调、方案整合
- 创建专用启动脚本start.sh
- 验证系统可正常运行在端口4174
- 实现代码复用率90%,符合预期目标

影响文件: web_frontend/food-order-demo/
技术栈: React 18 + TypeScript + Tailwind CSS + Zustand
2025-09-28 10:32:44 +08:00

37 lines
1.2 KiB
JavaScript

/// <reference lib="dom" />
/* global document */
const element = document.createElement('i')
/**
* @param {string} value
* @returns {string | false}
*/
export function decodeNamedCharacterReference(value) {
const characterReference = '&' + value + ';'
element.innerHTML = characterReference
const character = element.textContent
// Some named character references do not require the closing semicolon
// (`&not`, for instance), which leads to situations where parsing the assumed
// named reference of `&notit;` will result in the string `¬it;`.
// When we encounter a trailing semicolon after parsing, and the character
// reference to decode was not a semicolon (`&semi;`), we can assume that the
// matching was not complete.
if (
// @ts-expect-error: TypeScript is wrong that `textContent` on elements can
// yield `null`.
character.charCodeAt(character.length - 1) === 59 /* `;` */ &&
value !== 'semi'
) {
return false
}
// If the decoded string is equal to the input, the character reference was
// not valid.
// @ts-expect-error: TypeScript is wrong that `textContent` on elements can
// yield `null`.
return character === characterReference ? false : character
}