[{"data":1,"prerenderedAt":1557},["ShallowReactive",2],{"\u002Fwriting\u002Ffusionx":3},{"id":4,"title":5,"body":6,"date":1546,"description":172,"extension":1547,"intro":1548,"meta":1549,"navigation":899,"path":1550,"seo":1551,"stem":1552,"tags":1553,"__hash__":1556},"writing\u002Fwriting\u002Ffusionx.md","做梦也不敢想的 FusionX 研发感想",{"type":7,"value":8,"toc":1525},"minimark",[9,17,20,25,28,31,50,67,70,85,92,96,111,117,120,123,128,131,160,163,166,668,671,691,698,701,704,722,728,731,735,738,746,749,752,756,759,788,791,794,798,807,824,827,842,860,863,873,1026,1033,1338,1355,1359,1362,1365,1368,1371,1377,1380,1420,1423,1441,1444,1448,1451,1454,1457,1460,1468,1474,1481,1484,1487,1490,1493,1496,1499,1502,1505,1508,1511,1521],[10,11,12],"p",{},[13,14],"img",{"alt":15,"src":16},"FusionX 内部分享会","\u002Fimg\u002Ffusionx\u002Fslide-0.png",[10,18,19],{},"各位同学，今天想为大家带来关于 FusionX 研发过程中的感想。在 FusionX 团队和其他项目组的共同努力下，FusionX 于去年底发布了第一个正式版本，很快 FusionX 就将在第一个商业项目上被正式使用。今天我想谈一下在设计和建设 FusionX 的过程中我们的思路和想法，以及对 FusionX 未来迭代和发展的期望。",[21,22,24],"h2",{"id":23},"什么是低代码","什么是低代码？",[10,26,27],{},"在得到公司批准建设 FusionX 时，我们首先想要确定的问题就是「什么是低代码」。是的，这个问题看起来过于「小儿科」，但是理解低代码和低代码平台的定义对于我们希望把 FusionX 建设到何种程度——也就是能力边界在哪里，以及达到什么目标——来说是非常重要的。",[10,29,30],{},"我们先来看 Wikipedia 和 Forrester 给出的两个定义：",[32,33,34],"blockquote",{},[10,35,36,37,45,46,49],{},"低代码开发平台（LCDP）提供了一种允许开发者以",[38,39,40,41,44],"strong",{},"图形化界面（GUI）",[38,42,43],{},"和","配置式","的方式",[38,47,48],{},"快速开发","应用程序的环境，而不完全通过编写代码实现交付。\n—— Wikipedia",[32,51,52],{},[10,53,54,55,58,59,62,63,66],{},"低代码开发平台（LCDP）提供了一",[38,56,57],{},"快捷交付","业务应用的能力，而不需要开发者编写太多的代码，也",[38,60,61],{},"不需要","了解常规开发中的",[38,64,65],{},"前置工作","，例如编程语言和开发环境的配置等。\n—— Forrester",[10,68,69],{},"在这两个定义中，有一些共同点可以被我们提取出来，稍加总结如下：",[71,72,73,76,79,82],"ul",{},[74,75,40],"li",{},[74,77,78],{},"配置式（Configurable）",[74,80,81],{},"低门槛（Minimal upfront investment）",[74,83,84],{},"快速交付（Rapid delivery）",[10,86,87,88,91],{},"在 FusionX 的设计与开发过程中，项目团队的同事们始终将这四个特点所组成的定义作为我们低代码开发平台的出发点与落脚点。换句话说，FusionX 的目标就是",[38,89,90],{},"通过图形化界面和配置式的开发方式，实现低门槛的快速交付","。",[21,93,95],{"id":94},"fusionx-的构成","FusionX 的构成",[10,97,98,99,102,103,106,107,110],{},"刚才我们讲到，FusionX 的开发方式是基于图形化界面和配置式的，这需要我们首先建设一个低代码的 ",[38,100,101],{},"「开发工具」","；其次，FusionX 也需要考虑如何",[38,104,105],{},"存储","开发者建设的应用、以何种结构表示这些应用，以及最后：如何将存储的结构转变为用户可以正常使用并与之交互的「",[38,108,109],{},"运行时","」。",[10,112,113],{},[13,114],{"alt":115,"src":116},"FusionX 构成","\u002Fimg\u002Ffusionx\u002Fparts.png",[10,118,119],{},"显然，这张图里最核心的位置，就是 DSL。换句话说，使用开发工具建设应用，或者在运行时执行应用，都需要依赖于中间的、用于存储应用的数据结构。当开发者使用开发工具建设应用时，他们需要通过 GUI 来配置应用的组件、行为和属性，这些配置信息最终会被转换为可以被轻松存储的数据结构；而当应用需要被运行时执行时，在运行时存储在数据库中、符合约定的数据结构的数据来创建应用的实例，并执行应用的行为。",[10,121,122],{},"在 FusionX 中，我们称这种用于存储应用数据的结构为「Schema」。",[124,125,127],"h3",{"id":126},"schema","Schema",[10,129,130],{},"那么应当如何设计一个足以表示复杂应用程序的结构呢？我们不妨先看一下在一个应用中多有多少信息必须要被存储。",[71,132,133,136,139,142,145,148,151,154,157],{},[74,134,135],{},"一个应用包含多个组件，每个组件有自己的行为和属性；",[74,137,138],{},"组件之间可能有依赖关系，例如一个组件的行为依赖于另一个组件的属性；",[74,140,141],{},"组件之间可能发生嵌套，即一个组件（如 Tab）包含了另一个或一些组件；",[74,143,144],{},"应用可能有自己的全局状态，例如用户登录信息等；",[74,146,147],{},"应用可能有关联的数据表；",[74,149,150],{},"应用可能有自己的生命周期，例如启动时需要初始化一些数据，关闭时需要清理资源等；",[74,152,153],{},"应用可能有一些用户定义的全局函数，可以被组件或生命周期调用；",[74,155,156],{},"如果应用含有流转程序，那么还应当有流程。",[74,158,159],{},"...",[10,161,162],{},"在设计 FusionX 的过程中，我们首先明确的就是这些信息。从某种意义上来说，这也是一份需求清单，告诉我们要为 FusionX 开发哪些在 pro code 开发场景下非常常见的功能，算是为我们后续的开发工作奠定了基础。",[10,164,165],{},"最终，正如大家知道的，我们采用 JSON 结构表示应用的 Schema。一个 Schema 看上去可能是这个样子的：",[167,168,173],"pre",{"className":169,"code":170,"language":171,"meta":172,"style":172},"language-json shiki shiki-themes houston","{\n  \"version\": \"1\", \u002F\u002F 版本号，用于后续 schema 升级时的迁移策略\n  \"dataSources\": { \u002F\u002F 数据源，包括数据库、API 等\n    \"db\": [], \u002F\u002F 数据库表列表，每项包含数据库、表名等信息\n    \"api\": [], \u002F\u002F API 列表，每项包含 API 名称、URL、请求方法、请求参数等信息\n  },\n  \"functions\": [ \u002F\u002F 用户定义的全局函数\n    {\n      \"name\": \"myFunction\", \u002F\u002F 用户定义的函数名称\n      \"uid\": \"joa91a01kd86ns\",\n      \"desc\": \"\", \u002F\u002F 用户定义的函数备注\n      \u002F\u002F 函数体，包含 FusionX 的 API\n      \"body\": \"if ($values.age \u003C 18) { $widgets.someField.setEnabled(false) }\"\n    },\n    \u002F\u002F ...\n  ],\n  \"states\": { \u002F\u002F 全局状态，可以在函数、自定义校验、组件 options 等场景下通过`$state.`获取\n    \"user\": {\n      \"name\": \"admin\",\n      \"email\": \"admin@example.com\",\n      \"age\": 30,\n      \"dept\": 1,\n      \"role\": [1, 101, 102]\n    },\n    \u002F\u002F ...\n  },\n  \"componentsTree\": [ \u002F\u002F 组件树\n    {\n      \"uid\": \"dkf049pdk3f0hmhv\", \u002F\u002F 组件唯一标识，可以通过`$widgets.`获取组件\n      \"type\": \"Input\", \u002F\u002F 组件类型，不同类型的组件有不同的行为和属性\n      \"group\": \"form\", \u002F\u002F 组件所属的分组，用于在 GUI 中组织组件\n      \"title\": \"输入框\", \u002F\u002F 组件在 GUI 中的标题\n      \"props\": { \u002F\u002F 组件的属性，用于配置组件的行为和外观\n        \"field\": { \u002F\u002F 表单组件特有属性\n          \"name\": \"name\", \u002F\u002F 字段名，也可以通过`$widgets.`获取组件\n          \"label\": \"姓名\",\n          \"required\": true\n        },\n        \"maxlength\": 10,\n        \"placeholder\": \"请输入姓名\",\n        \"events\": {} \u002F\u002F 组件的事件回调，可以绑定函数\n      }\n    },\n    \u002F\u002F ...\n  ],\n}\n","json","",[174,175,176,185,206,218,230,241,247,259,265,281,295,311,317,328,334,340,346,357,366,378,391,404,417,441,446,451,456,467,472,487,503,519,535,546,557,573,586,597,603,616,629,641,647,652,657,662],"code",{"__ignoreMap":172},[177,178,181],"span",{"class":179,"line":180},"line",1,[177,182,184],{"class":183},"sLo_3","{\n",[177,186,188,192,195,199,202],{"class":179,"line":187},2,[177,189,191],{"class":190},"sb16X","  \"version\"",[177,193,194],{"class":183},": ",[177,196,198],{"class":197},"se2J0","\"1\"",[177,200,201],{"class":183},", ",[177,203,205],{"class":204},"sy89t","\u002F\u002F 版本号，用于后续 schema 升级时的迁移策略\n",[177,207,209,212,215],{"class":179,"line":208},3,[177,210,211],{"class":190},"  \"dataSources\"",[177,213,214],{"class":183},": { ",[177,216,217],{"class":204},"\u002F\u002F 数据源，包括数据库、API 等\n",[177,219,221,224,227],{"class":179,"line":220},4,[177,222,223],{"class":190},"    \"db\"",[177,225,226],{"class":183},": [], ",[177,228,229],{"class":204},"\u002F\u002F 数据库表列表，每项包含数据库、表名等信息\n",[177,231,233,236,238],{"class":179,"line":232},5,[177,234,235],{"class":190},"    \"api\"",[177,237,226],{"class":183},[177,239,240],{"class":204},"\u002F\u002F API 列表，每项包含 API 名称、URL、请求方法、请求参数等信息\n",[177,242,244],{"class":179,"line":243},6,[177,245,246],{"class":183},"  },\n",[177,248,250,253,256],{"class":179,"line":249},7,[177,251,252],{"class":190},"  \"functions\"",[177,254,255],{"class":183},": [ ",[177,257,258],{"class":204},"\u002F\u002F 用户定义的全局函数\n",[177,260,262],{"class":179,"line":261},8,[177,263,264],{"class":183},"    {\n",[177,266,268,271,273,276,278],{"class":179,"line":267},9,[177,269,270],{"class":190},"      \"name\"",[177,272,194],{"class":183},[177,274,275],{"class":197},"\"myFunction\"",[177,277,201],{"class":183},[177,279,280],{"class":204},"\u002F\u002F 用户定义的函数名称\n",[177,282,284,287,289,292],{"class":179,"line":283},10,[177,285,286],{"class":190},"      \"uid\"",[177,288,194],{"class":183},[177,290,291],{"class":197},"\"joa91a01kd86ns\"",[177,293,294],{"class":183},",\n",[177,296,298,301,303,306,308],{"class":179,"line":297},11,[177,299,300],{"class":190},"      \"desc\"",[177,302,194],{"class":183},[177,304,305],{"class":197},"\"\"",[177,307,201],{"class":183},[177,309,310],{"class":204},"\u002F\u002F 用户定义的函数备注\n",[177,312,314],{"class":179,"line":313},12,[177,315,316],{"class":204},"      \u002F\u002F 函数体，包含 FusionX 的 API\n",[177,318,320,323,325],{"class":179,"line":319},13,[177,321,322],{"class":190},"      \"body\"",[177,324,194],{"class":183},[177,326,327],{"class":197},"\"if ($values.age \u003C 18) { $widgets.someField.setEnabled(false) }\"\n",[177,329,331],{"class":179,"line":330},14,[177,332,333],{"class":183},"    },\n",[177,335,337],{"class":179,"line":336},15,[177,338,339],{"class":204},"    \u002F\u002F ...\n",[177,341,343],{"class":179,"line":342},16,[177,344,345],{"class":183},"  ],\n",[177,347,349,352,354],{"class":179,"line":348},17,[177,350,351],{"class":190},"  \"states\"",[177,353,214],{"class":183},[177,355,356],{"class":204},"\u002F\u002F 全局状态，可以在函数、自定义校验、组件 options 等场景下通过`$state.`获取\n",[177,358,360,363],{"class":179,"line":359},18,[177,361,362],{"class":190},"    \"user\"",[177,364,365],{"class":183},": {\n",[177,367,369,371,373,376],{"class":179,"line":368},19,[177,370,270],{"class":190},[177,372,194],{"class":183},[177,374,375],{"class":197},"\"admin\"",[177,377,294],{"class":183},[177,379,381,384,386,389],{"class":179,"line":380},20,[177,382,383],{"class":190},"      \"email\"",[177,385,194],{"class":183},[177,387,388],{"class":197},"\"admin@example.com\"",[177,390,294],{"class":183},[177,392,394,397,399,402],{"class":179,"line":393},21,[177,395,396],{"class":190},"      \"age\"",[177,398,194],{"class":183},[177,400,401],{"class":197},"30",[177,403,294],{"class":183},[177,405,407,410,412,415],{"class":179,"line":406},22,[177,408,409],{"class":190},"      \"dept\"",[177,411,194],{"class":183},[177,413,414],{"class":197},"1",[177,416,294],{"class":183},[177,418,420,423,426,428,430,433,435,438],{"class":179,"line":419},23,[177,421,422],{"class":190},"      \"role\"",[177,424,425],{"class":183},": [",[177,427,414],{"class":197},[177,429,201],{"class":183},[177,431,432],{"class":197},"101",[177,434,201],{"class":183},[177,436,437],{"class":197},"102",[177,439,440],{"class":183},"]\n",[177,442,444],{"class":179,"line":443},24,[177,445,333],{"class":183},[177,447,449],{"class":179,"line":448},25,[177,450,339],{"class":204},[177,452,454],{"class":179,"line":453},26,[177,455,246],{"class":183},[177,457,459,462,464],{"class":179,"line":458},27,[177,460,461],{"class":190},"  \"componentsTree\"",[177,463,255],{"class":183},[177,465,466],{"class":204},"\u002F\u002F 组件树\n",[177,468,470],{"class":179,"line":469},28,[177,471,264],{"class":183},[177,473,475,477,479,482,484],{"class":179,"line":474},29,[177,476,286],{"class":190},[177,478,194],{"class":183},[177,480,481],{"class":197},"\"dkf049pdk3f0hmhv\"",[177,483,201],{"class":183},[177,485,486],{"class":204},"\u002F\u002F 组件唯一标识，可以通过`$widgets.`获取组件\n",[177,488,490,493,495,498,500],{"class":179,"line":489},30,[177,491,492],{"class":190},"      \"type\"",[177,494,194],{"class":183},[177,496,497],{"class":197},"\"Input\"",[177,499,201],{"class":183},[177,501,502],{"class":204},"\u002F\u002F 组件类型，不同类型的组件有不同的行为和属性\n",[177,504,506,509,511,514,516],{"class":179,"line":505},31,[177,507,508],{"class":190},"      \"group\"",[177,510,194],{"class":183},[177,512,513],{"class":197},"\"form\"",[177,515,201],{"class":183},[177,517,518],{"class":204},"\u002F\u002F 组件所属的分组，用于在 GUI 中组织组件\n",[177,520,522,525,527,530,532],{"class":179,"line":521},32,[177,523,524],{"class":190},"      \"title\"",[177,526,194],{"class":183},[177,528,529],{"class":197},"\"输入框\"",[177,531,201],{"class":183},[177,533,534],{"class":204},"\u002F\u002F 组件在 GUI 中的标题\n",[177,536,538,541,543],{"class":179,"line":537},33,[177,539,540],{"class":190},"      \"props\"",[177,542,214],{"class":183},[177,544,545],{"class":204},"\u002F\u002F 组件的属性，用于配置组件的行为和外观\n",[177,547,549,552,554],{"class":179,"line":548},34,[177,550,551],{"class":190},"        \"field\"",[177,553,214],{"class":183},[177,555,556],{"class":204},"\u002F\u002F 表单组件特有属性\n",[177,558,560,563,565,568,570],{"class":179,"line":559},35,[177,561,562],{"class":190},"          \"name\"",[177,564,194],{"class":183},[177,566,567],{"class":197},"\"name\"",[177,569,201],{"class":183},[177,571,572],{"class":204},"\u002F\u002F 字段名，也可以通过`$widgets.`获取组件\n",[177,574,576,579,581,584],{"class":179,"line":575},36,[177,577,578],{"class":190},"          \"label\"",[177,580,194],{"class":183},[177,582,583],{"class":197},"\"姓名\"",[177,585,294],{"class":183},[177,587,589,592,594],{"class":179,"line":588},37,[177,590,591],{"class":190},"          \"required\"",[177,593,194],{"class":183},[177,595,596],{"class":197},"true\n",[177,598,600],{"class":179,"line":599},38,[177,601,602],{"class":183},"        },\n",[177,604,606,609,611,614],{"class":179,"line":605},39,[177,607,608],{"class":190},"        \"maxlength\"",[177,610,194],{"class":183},[177,612,613],{"class":197},"10",[177,615,294],{"class":183},[177,617,619,622,624,627],{"class":179,"line":618},40,[177,620,621],{"class":190},"        \"placeholder\"",[177,623,194],{"class":183},[177,625,626],{"class":197},"\"请输入姓名\"",[177,628,294],{"class":183},[177,630,632,635,638],{"class":179,"line":631},41,[177,633,634],{"class":190},"        \"events\"",[177,636,637],{"class":183},": {} ",[177,639,640],{"class":204},"\u002F\u002F 组件的事件回调，可以绑定函数\n",[177,642,644],{"class":179,"line":643},42,[177,645,646],{"class":183},"      }\n",[177,648,650],{"class":179,"line":649},43,[177,651,333],{"class":183},[177,653,655],{"class":179,"line":654},44,[177,656,339],{"class":204},[177,658,660],{"class":179,"line":659},45,[177,661,345],{"class":183},[177,663,665],{"class":179,"line":664},46,[177,666,667],{"class":183},"}\n",[10,669,670],{},"当用户在低代码设计器中对应用进行设计时，其本质是对 Schema 结构的修改，即：",[71,672,673,676,679,682,685,688],{},[74,674,675],{},"当用户新增组件时，体现为在 Schema 中插入新元素；",[74,677,678],{},"当用户修改组件的配置项时，体现为修改 Schema 中对应的元素中的某个属性；",[74,680,681],{},"当用户调整两个组件的顺序时，体现为修改 Schema 中对应的两个元素的下标；",[74,683,684],{},"当用户删除组件时，体现为从 Schema 中移除对应的元素；",[74,686,687],{},"当用户复制组件时，体现为从 Schema 中复制指定的元素并插入到该元素后方，同时重新生成组件的唯一标识 UID；",[74,689,690],{},"......",[10,692,693,694,697],{},"Schema 的结构并非只是一个存在于项目中的",[174,695,696],{},"d.ts","声明，而是由我们经过讨论并起草《低代码协议》后确定的。《低代码协议》定义了采用低代码的开发活动时涉及的概念、术语、接口等，并为我们提供了一份从工程学角度描述和解释我们工作的规范。",[124,699,700],{"id":700},"开发环境",[10,702,703],{},"刚才我们讲到，如果将 Schema 看做一门 DSL，那么开发环境就是用于编写和执行这种 DSL 的工具。它产生 Schema，可能还会像 linter 和 formatter 一样根据既定的规则和标准对 Schema 进行转换和调整，最重要的是，它需要能够执行 Schema，将其转换成浏览器可以执行的 JS、HTML 和 CSS。",[10,705,706,707,43,710,713,714,717,718,721],{},"在 FusionX 中，开发环境主要由编辑器和解释器组成，这对应了我们发布的 npm 包中",[174,708,709],{},"@fusionx\u002Feditor",[174,711,712],{},"@fusionx\u002Finterpreter","。前者提供了用于搭建 GUI 和配置界面的组件，也提供了开箱即用的",[174,715,716],{},"\u003CFusionXEditor \u002F>","组件；后者提供了一系列 API 和",[174,719,720],{},"\u003CFuxRenderer \u002F>","组件来在运行时根据 Schema 渲染应用程序。",[10,723,724],{},[13,725],{"alt":726,"src":727},"FusionX Editor","\u002Fimg\u002Ffusionx\u002Feditor.png",[10,729,730],{},"通过编辑器，开发者可以可视化构建应用程序。而应用程序中的组件及它们的属性、行为和相对位置等都被记录在了藉由编辑器生成的 Schema 中。这就是使用 FusionX 进行开发的核心。",[124,732,734],{"id":733},"schema-的消费aot-or-jit","Schema 的消费：AOT or JIT？",[10,736,737],{},"从 Schema 的消费角度讲，通常有两种形式：",[71,739,740,743],{},[74,741,742],{},"静态编译（AOT），即在运行时之前，将 Schema 转换为浏览器可以执行的 JS、HTML 和 CSS。",[74,744,745],{},"动态编译（JIT），即在运行时，根据 Schema 动态生成 JS、HTML 和 CSS。",[10,747,748],{},"在设计之初，我们决定在 1.0.0 版本中优先实现动态编译。这主要是考虑到 FusionX 的首要任务是可以被立刻 drop in，替换现有的政务场景下服务表单的开发。这是一个典型的「流程+表单」的应用场景。这个场景的特点是其模式相对固定，属于页面的或业务的一个部分，且表单和流程的变更相对其他场景都更频繁。在采用静态编译的情况下，生成的代码无法再次被读取，一旦开发者对生成的代码进行了修改，再次发生变更时会覆盖修改的内容。",[10,750,751],{},"但是，静态编译也存在无法替代的优点，比如可以获得原生的性能表现、可以在编译阶段发现错误避免运行时的崩溃；对于修改频次低的业务，生成的代码可以由工程师已进行二次开发来满足 low code 下实现复杂的需求。当然，静态编译的形式也可以引入 linter 和 formatter 到编译链中对代码进行优化与检查。当开发包含完整生命周期的应用而非局限于表单部分时，静态编译是一个更好的选择。在最后我们会讨论 FusionX 2.0 的展望与规划，我们期望在 2.0 版本中可以实现完整的应用级别低代码开发，因此静态编译是必须要提上日程的。",[21,753,755],{"id":754},"构建-ui-无关的低代码引擎","构建 UI 无关的低代码引擎",[10,757,758],{},"当前我们所面临的一个现状就是各个团队都在使用不同的 UI 组件库，也有各自形成的可复用资产。当然，我们希望能在未来实现组织范围内的统一资产管理和维护体系，但是在现阶段，隔离的 UI 资产要求 FusionX 必须具备 UI 无关性。",[10,760,761,762,769,770,773,774,777,778,783,784,787],{},"不同的组件库之间，组件的类型，它们的属性名和可配置的值等都是不同的。例如在 ",[763,764,768],"a",{"href":765,"rel":766},"https:\u002F\u002Farco.design\u002F",[767],"nofollow","Arco Design"," 中，有",[174,771,772],{},"InputTag","组件，而在 Ant Design 中则没有；在 Element Plus 中，",[174,775,776],{},"Input","没有无边框模式，但是在 ",[763,779,782],{"href":780,"rel":781},"https:\u002F\u002Ftdesign.tencent.com\u002F",[767],"TDesign"," 中则由",[174,785,786],{},"borderless","属性来控制。此外，各团队都有自行封装的组件，这些组件都各有其特殊属性。",[10,789,790],{},"好在，Schema 本身作为 JSON 结构是不依赖特定组件库的。关键在于让编辑器能够支持自定义组件的配置项、让编译器能够识别自定义的组件和属性并正确渲染。",[10,792,793],{},"在 FusionX 中，我们通过实现「入料」机制来解决这个问题。",[124,795,797],{"id":796},"入料","「入料」",[10,799,800,801,806],{},"「入料」这个名词来自于阿里的",[763,802,805],{"href":803,"rel":804},"https:\u002F\u002Flowcode-engine.cn\u002F",[767],"Low Code Engine","。在 FusionX 中，「入料」特指将不同的组件按照规则传入 FusionX 并被处理成可供编辑器和编译器使用的组件的过程。",[10,808,809,810,813,814,816,817,820,821,823],{},"首先来看一个简单的例子。FusionX 使用 TDesign 作为默认组件库，但假设有另一个",[174,811,812],{},"MyInput","组件，我们希望最终能够渲染和使用",[174,815,812],{},"来代替 TDesign 中的",[174,818,819],{},"TInput","。这个时候，我们需要把",[174,822,812],{},"入料。",[10,825,826],{},"入料的过程可以简单总结为：",[828,829,830,836],"ol",{},[74,831,832,833,835],{},"指定如何渲染",[174,834,812],{},"组件。",[74,837,838,839,841],{},"指定可以如何配置",[174,840,812],{},"组件的属性和行为。",[10,843,844,845,848,849,43,852,855,856,859],{},"在 FusionX 中，每一个低代码组件基本都由运行时文件和配置时文件构成。可以看到",[174,846,847],{},"@fusionx\u002Fcore\u002Finternal\u002Fmaterials","目录下，每一个组件目录中都有对应的",[174,850,851],{},"setter.vue",[174,853,854],{},"index.vue","，当然，部分表单组件还有阅读模式下的渲染文件",[174,857,858],{},"view.vue","，这种情况暂时不纳入讨论。",[10,861,862],{},"在进行自定义组件入料时，我们需要指定组件的渲染状态和配置状态。也就是说，对于每一个组件，需要创建两个组件分别告诉 FusionX 应当如何描述和渲染组件。",[10,864,865,866,869,870,872],{},"然后，在注册 FusionX 的时候，通过传入",[174,867,868],{},"options.materials","配置",[174,871,812],{},"：",[167,874,878],{"className":875,"code":876,"language":877,"meta":172,"style":172},"language-ts shiki shiki-themes houston","import FusionX from '@fusionx\u002Fcore'\n\napp.use(FusionX, {\n  materials: [\n    {\n      name: 'MyInput',\n      title: '自定义输入框',\n      group: 'form\u002Fbasic',\n      main: () => import('@some-package\u002Fmy-input\u002Findex.vue'),\n      setter: () => import('@some-package\u002Fmy-input\u002Fsetter.vue')\n    }\n  ]\n})\n","ts",[174,879,880,895,901,922,930,934,946,958,970,992,1011,1016,1021],{"__ignoreMap":172},[177,881,882,886,889,892],{"class":179,"line":180},[177,883,885],{"class":884},"sqF6k","import",[177,887,888],{"class":190}," FusionX",[177,890,891],{"class":884}," from",[177,893,894],{"class":197}," '@fusionx\u002Fcore'\n",[177,896,897],{"class":179,"line":187},[177,898,900],{"emptyLinePlaceholder":899},true,"\n",[177,902,903,906,909,913,916,919],{"class":179,"line":208},[177,904,905],{"class":190},"app",[177,907,908],{"class":183},".",[177,910,912],{"class":911},"stHQG","use",[177,914,915],{"class":183},"(",[177,917,918],{"class":190},"FusionX",[177,920,921],{"class":183},", {\n",[177,923,924,927],{"class":179,"line":220},[177,925,926],{"class":190},"  materials",[177,928,929],{"class":183},": [\n",[177,931,932],{"class":179,"line":232},[177,933,264],{"class":183},[177,935,936,939,941,944],{"class":179,"line":243},[177,937,938],{"class":190},"      name",[177,940,194],{"class":183},[177,942,943],{"class":197},"'MyInput'",[177,945,294],{"class":183},[177,947,948,951,953,956],{"class":179,"line":249},[177,949,950],{"class":190},"      title",[177,952,194],{"class":183},[177,954,955],{"class":197},"'自定义输入框'",[177,957,294],{"class":183},[177,959,960,963,965,968],{"class":179,"line":261},[177,961,962],{"class":190},"      group",[177,964,194],{"class":183},[177,966,967],{"class":197},"'form\u002Fbasic'",[177,969,294],{"class":183},[177,971,972,975,978,981,984,986,989],{"class":179,"line":267},[177,973,974],{"class":911},"      main",[177,976,977],{"class":183},": () ",[177,979,980],{"class":884},"=>",[177,982,983],{"class":911}," import",[177,985,915],{"class":183},[177,987,988],{"class":197},"'@some-package\u002Fmy-input\u002Findex.vue'",[177,990,991],{"class":183},"),\n",[177,993,994,997,999,1001,1003,1005,1008],{"class":179,"line":283},[177,995,996],{"class":911},"      setter",[177,998,977],{"class":183},[177,1000,980],{"class":884},[177,1002,983],{"class":911},[177,1004,915],{"class":183},[177,1006,1007],{"class":197},"'@some-package\u002Fmy-input\u002Fsetter.vue'",[177,1009,1010],{"class":183},")\n",[177,1012,1013],{"class":179,"line":297},[177,1014,1015],{"class":183},"    }\n",[177,1017,1018],{"class":179,"line":313},[177,1019,1020],{"class":183},"  ]\n",[177,1022,1023],{"class":179,"line":319},[177,1024,1025],{"class":183},"})\n",[10,1027,1028,1029,1032],{},"对于没有特殊配置逻辑的组件，一个更直接的方式是直接通过向",[174,1030,1031],{},"setter","属性传入用于渲染配置项的 JS 对象。支持的属性包括：",[167,1034,1036],{"className":875,"code":1035,"language":877,"meta":172,"style":172},"export interface SetterMeta {\n  \u002F** Props of the material that can be config in the setter. *\u002F\n  props: Array\u003C{\n    \u002F** Setter type. *\u002F\n    type: 'input' | 'select' | 'switch' | 'number' | 'code'\n    \u002F** Setter label. *\u002F\n    label?: string\n    \u002F** Setter name. Corresponds to the property name of the material. *\u002F\n    name?: string\n    \u002F** Setter props. e.g. `options` for `select` type; `min`, `max` for `number` type. *\u002F\n    setterProps?: Record\u003Cstring, unknown>\n    defaultValue?: unknown\n    \u002F** Whether the setter value can be bound to a state\u002Fexpression. *\u002F\n    allowBinding?: boolean\n    \u002F**\n     * Whether the setter should be rendered.\n     * e.g. The `max` prop setter of the select widget should not be rendered when the `multiple` prop is `false`\n     * @param props The props of the material.\n     * @returns Whether the setter should be rendered.\n     *\u002F\n    shouldRender?: (props: Record\u003Cstring, unknown>) => boolean\n  }>\n  \u002F** Additional config of the material. *\u002F\n  config: {\n    supports?: {\n      \u002F** Supported event names of the material. *\u002F\n      events?: string[]\n    }\n  }\n}\n",[174,1037,1038,1053,1058,1071,1076,1107,1112,1125,1130,1141,1146,1172,1184,1189,1201,1206,1211,1216,1232,1242,1247,1280,1285,1290,1297,1306,1311,1325,1329,1334],{"__ignoreMap":172},[177,1039,1040,1043,1046,1050],{"class":179,"line":180},[177,1041,1042],{"class":884},"export",[177,1044,1045],{"class":884}," interface",[177,1047,1049],{"class":1048},"s8HWQ"," SetterMeta",[177,1051,1052],{"class":183}," {\n",[177,1054,1055],{"class":179,"line":187},[177,1056,1057],{"class":204},"  \u002F** Props of the material that can be config in the setter. *\u002F\n",[177,1059,1060,1063,1065,1068],{"class":179,"line":208},[177,1061,1062],{"class":190},"  props",[177,1064,194],{"class":183},[177,1066,1067],{"class":1048},"Array",[177,1069,1070],{"class":183},"\u003C{\n",[177,1072,1073],{"class":179,"line":220},[177,1074,1075],{"class":204},"    \u002F** Setter type. *\u002F\n",[177,1077,1078,1081,1083,1086,1089,1092,1094,1097,1099,1102,1104],{"class":179,"line":232},[177,1079,1080],{"class":190},"    type",[177,1082,194],{"class":183},[177,1084,1085],{"class":197},"'input'",[177,1087,1088],{"class":183}," | ",[177,1090,1091],{"class":197},"'select'",[177,1093,1088],{"class":183},[177,1095,1096],{"class":197},"'switch'",[177,1098,1088],{"class":183},[177,1100,1101],{"class":197},"'number'",[177,1103,1088],{"class":183},[177,1105,1106],{"class":197},"'code'\n",[177,1108,1109],{"class":179,"line":243},[177,1110,1111],{"class":204},"    \u002F** Setter label. *\u002F\n",[177,1113,1114,1117,1120,1122],{"class":179,"line":249},[177,1115,1116],{"class":190},"    label",[177,1118,1119],{"class":884},"?",[177,1121,194],{"class":183},[177,1123,1124],{"class":1048},"string\n",[177,1126,1127],{"class":179,"line":261},[177,1128,1129],{"class":204},"    \u002F** Setter name. Corresponds to the property name of the material. *\u002F\n",[177,1131,1132,1135,1137,1139],{"class":179,"line":267},[177,1133,1134],{"class":190},"    name",[177,1136,1119],{"class":884},[177,1138,194],{"class":183},[177,1140,1124],{"class":1048},[177,1142,1143],{"class":179,"line":283},[177,1144,1145],{"class":204},"    \u002F** Setter props. e.g. `options` for `select` type; `min`, `max` for `number` type. *\u002F\n",[177,1147,1148,1151,1153,1155,1158,1161,1164,1166,1169],{"class":179,"line":297},[177,1149,1150],{"class":190},"    setterProps",[177,1152,1119],{"class":884},[177,1154,194],{"class":183},[177,1156,1157],{"class":1048},"Record",[177,1159,1160],{"class":183},"\u003C",[177,1162,1163],{"class":1048},"string",[177,1165,201],{"class":183},[177,1167,1168],{"class":1048},"unknown",[177,1170,1171],{"class":183},">\n",[177,1173,1174,1177,1179,1181],{"class":179,"line":313},[177,1175,1176],{"class":190},"    defaultValue",[177,1178,1119],{"class":884},[177,1180,194],{"class":183},[177,1182,1183],{"class":1048},"unknown\n",[177,1185,1186],{"class":179,"line":319},[177,1187,1188],{"class":204},"    \u002F** Whether the setter value can be bound to a state\u002Fexpression. *\u002F\n",[177,1190,1191,1194,1196,1198],{"class":179,"line":330},[177,1192,1193],{"class":190},"    allowBinding",[177,1195,1119],{"class":884},[177,1197,194],{"class":183},[177,1199,1200],{"class":1048},"boolean\n",[177,1202,1203],{"class":179,"line":336},[177,1204,1205],{"class":204},"    \u002F**\n",[177,1207,1208],{"class":179,"line":342},[177,1209,1210],{"class":204},"     * Whether the setter should be rendered.\n",[177,1212,1213],{"class":179,"line":348},[177,1214,1215],{"class":204},"     * e.g. The `max` prop setter of the select widget should not be rendered when the `multiple` prop is `false`\n",[177,1217,1218,1221,1225,1229],{"class":179,"line":359},[177,1219,1220],{"class":204},"     * ",[177,1222,1224],{"class":1223},"sZHg5","@param",[177,1226,1228],{"class":1227},"smONe"," props",[177,1230,1231],{"class":204}," The props of the material.\n",[177,1233,1234,1236,1239],{"class":179,"line":368},[177,1235,1220],{"class":204},[177,1237,1238],{"class":1223},"@returns",[177,1240,1241],{"class":204}," Whether the setter should be rendered.\n",[177,1243,1244],{"class":179,"line":380},[177,1245,1246],{"class":204},"     *\u002F\n",[177,1248,1249,1252,1254,1257,1260,1262,1264,1266,1268,1270,1272,1275,1277],{"class":179,"line":393},[177,1250,1251],{"class":911},"    shouldRender",[177,1253,1119],{"class":884},[177,1255,1256],{"class":183},": (",[177,1258,1259],{"class":1227},"props",[177,1261,194],{"class":183},[177,1263,1157],{"class":1048},[177,1265,1160],{"class":183},[177,1267,1163],{"class":1048},[177,1269,201],{"class":183},[177,1271,1168],{"class":1048},[177,1273,1274],{"class":183},">) ",[177,1276,980],{"class":884},[177,1278,1279],{"class":1048}," boolean\n",[177,1281,1282],{"class":179,"line":406},[177,1283,1284],{"class":183},"  }>\n",[177,1286,1287],{"class":179,"line":419},[177,1288,1289],{"class":204},"  \u002F** Additional config of the material. *\u002F\n",[177,1291,1292,1295],{"class":179,"line":443},[177,1293,1294],{"class":190},"  config",[177,1296,365],{"class":183},[177,1298,1299,1302,1304],{"class":179,"line":448},[177,1300,1301],{"class":190},"    supports",[177,1303,1119],{"class":884},[177,1305,365],{"class":183},[177,1307,1308],{"class":179,"line":453},[177,1309,1310],{"class":204},"      \u002F** Supported event names of the material. *\u002F\n",[177,1312,1313,1316,1318,1320,1322],{"class":179,"line":458},[177,1314,1315],{"class":190},"      events",[177,1317,1119],{"class":884},[177,1319,194],{"class":183},[177,1321,1163],{"class":1048},[177,1323,1324],{"class":183},"[]\n",[177,1326,1327],{"class":179,"line":469},[177,1328,1015],{"class":183},[177,1330,1331],{"class":179,"line":474},[177,1332,1333],{"class":183},"  }\n",[177,1335,1336],{"class":179,"line":489},[177,1337,667],{"class":183},[10,1339,1340,1341,1344,1345,1348,1349,1351,1352,1354],{},"在大多数情况下，入料的组件可配置项完全可以用",[174,1342,1343],{},"SetterMeta","的结构来描述。只有对于部分组件，配置面板中具有特殊逻辑时（例如",[174,1346,1347],{},"Tabs","组件中，有定义标签页的功能）才推荐向",[174,1350,1031],{},"传入一个用于配置的 Vue 组件。讲到这大家就应该知道了，",[174,1353,1343],{},"本身也像是 Schema，配置面板的实现其实也是引用了 FusionX 中的编译或者说渲染的逻辑。",[21,1356,1358],{"id":1357},"灵活性策略与-pro-code-集成","灵活性策略：与 pro code 集成",[10,1360,1361],{},"FusionX 的研发过程得到了各个项目团队的鼎力支持，我们的人手也抽调自各团队。但即便如此，FusionX 也无法保证 100% 覆盖所有可以使用 pro code 研发的场景。针对我们业务中复杂的需求，我们一方面要考虑如何在 FusionX 中以一种相对简化的、无需专业前端工程师也能实现的方式呈现，另一方面也要考虑如何在 pro code 的开发环境中使用 FusionX 提供的能力。",[124,1363,1364],{"id":1364},"编辑器内能力",[10,1366,1367],{},"首先，在 FusionX 中，我们提供了数据源和函数。这是两个强大的功能，分别用于从外部获取数据和在应用中执行自定义逻辑。",[10,1369,1370],{},"FusionX 编辑器中，数据源会在特定的时刻执行，其返回值可以被绑定到组件的属性上；而函数则可以被绑定到组件的事件、应用的生命周期或者表单的校验上。对于常见的需求：比如「根据用户输入的两个时间自动计算差值」「如果 A 的值超过某个数时就不显示 B」「如果 C 的值变更，那么下拉选单 D 的选项会被替换为另一个数组」等，均可以通过数据源、函数或两者的搭配实现。",[10,1372,1373],{},[13,1374],{"alt":1375,"src":1376},"为下拉选框组件的 onChange 事件绑定函数","\u002Fimg\u002Ffusionx\u002Ffx-bind.png",[10,1378,1379],{},"在函数中，FusionX 向开发者暴露了部分 API，用于在函数中访问和操作组件和应用的状态。下面的图展示了其中的部分：",[71,1381,1382,1388,1394,1404,1410],{},[74,1383,1384,1387],{},[174,1385,1386],{},"$values","：获取表单中所有组件的值。",[74,1389,1390,1393],{},[174,1391,1392],{},"$state","：获取数据源的状态值。",[74,1395,1396,1399,1400,1403],{},[174,1397,1398],{},"$dayjs","：同全局的",[174,1401,1402],{},"dayjs","函数。",[74,1405,1406,1409],{},[174,1407,1408],{},"$mode","：当前应用渲染的模式，往往用于在不同渲染环境下行为不一致的逻辑（例如事项办理与事项审核两个状态）。",[74,1411,1412,1415,1416,1419],{},[174,1413,1414],{},"$refs","：获取所有设置了引用的组件的引用。可以通过",[174,1417,1418],{},"$refs.\u003C组件引用>.","来调用部分组件暴露的方法。",[124,1421,1422],{"id":1422},"组件",[10,1424,1425,1426,1429,1430,1433,1434,1436,1437,1440],{},"对于需要在业务中部分使用 FusionX 进行渲染的场景，调用 FusionX 提供的组件以及它们的实例方法也可以实现一些特殊需求。例如，对于呼声很高的申报列表开发，我们就可以通过引入 FusionX 提供的",[174,1427,1428],{},"\u003CApplyList \u002F>","并传入",[174,1431,1432],{},"appId","来快速实现一个带有筛选表单、可配置列、分页且可以正常与业务的低代码部分交互的列表；再比如，有项目团队曾经希望避免调用 FusionX 内部表单组件的提交，而是先获取到数据，这可以通过",[174,1435,720],{},"的",[174,1438,1439],{},"ref.$refs.\u003C表单组件>.getFormData()","方法实现。",[10,1442,1443],{},"通过结合两个与 pro code 的集成维度所提供的能力，目前来说 FusionX 足以满足大部分场景的需求。",[21,1445,1447],{"id":1446},"面向未来fusionx-20","面向未来：FusionX 2.0",[10,1449,1450],{},"在 FusionX 发布第一个版本时，我和团队成员都有非常多的想法。其中一部分无疑是关于 FusionX 如何演变来支撑后续的业务发展。今天的最后我想分享一下，如果资源允许的情况下，FusionX 2.0 会带来哪些变化。",[124,1452,1453],{"id":1453},"重构",[10,1455,1456],{},"经过一段时间的使用，也包括项目团队对各业务项目使用 FusionX 开发的过程的「视奸」，有些问题得以被迅速暴露出来。我们希望在 2.0 能够重构这些部分，其中包括大家已经提出来的函数编辑器的性能问题等。",[10,1458,1459],{},"下图展示了我们预计重构的部分功能点。我们也希望在现阶段，各位能积极为我们提供反馈意见。",[10,1461,1462,1463,1467],{},"但其实，说到重构，在 FusionX 第一个版本为期半年的开发过程中，前端进行了两次重构。我不会深入设计模式和整洁代码这类技术细节来探讨重构的内容和最终成果。但我们要问一个问题：为什么要在",[1464,1465,1466],"em",{},"开发时","重构？",[10,1469,1470,1471,91],{},"很简单，因为我们不会在“重构时”重构。我们平常经常说的“先这样吧，有空再改”是一句彻头彻尾的谎话。根本不会有单独的时间用于重构——在项目中时间紧迫，我们会抱有侥幸，认为时间这么紧张，不是重构的时机；而当项目的冲刺期过去，我们会想已经过去的事情不必再次提起，因而就让往事随风而去。所以，",[38,1472,1473],{},"永远不会有重构的时机",[10,1475,1476,1477,1480],{},"有的同事可能会说：“可是我",[1464,1478,1479],{},"真的很忙","”！",[10,1482,1483],{},"相信我，我也是，我们都是。但时间紧张并不是进行妥协的借口，因为进行妥协并不能够真的缩短工期。即便可以，面对几乎 100% 需要调整的需求，所节约的时间将在日后的修改和维护中因为技术债务的存在而加倍偿还。我们作为专业的技术人员，不能够因为妥协而丧失我们的专业性。",[124,1485,1486],{"id":1486},"静态编译",[10,1488,1489],{},"我们要在 2.0 为大家带来的一个重磅更新就是对静态编译的支持。这个在刚才已经讲到过，静态编译是通往应用级低代码开发的基石，毕竟我们不可能整个系统全部建立在动态渲染的 JIT 机制上，那样不仅性能会受到影响，视觉上因动态加载和渲染导致的 CLS 也会增加。",[124,1491,1492],{"id":1492},"插件与生态",[10,1494,1495],{},"在 FusionX 2.0 中，我们将支持插件机制，允许开发者为 FusionX 开发插件。从技术角度说，插件是一个 JS 对象，可以在注册 FusionX 的时候传入。插件本身由一系列生命周期钩子构成，因此可以在不同的时候执行不同的逻辑。",[10,1497,1498],{},"在目前的版本中，我们已经在为这一点进行尝试。例如 FusionX 暴露的 API，届时都可以被插件调用；插件作用的场景和生命周期也已经被明确。具体来说，一个 FusionX 插件可以在编辑器中作用，也可以在运行时生效；可以在编译过程中对 Schema 进行转换，也可以在用户提交表单时拦截数据。",[10,1500,1501],{},"在 FusionX 2.0 发布时，也会内置一个插件用于演示插件能力。这个插件会在 FusionX 编辑态自动加载，以树状形式展示当前页面上的组件树结构，以及每一个节点依赖的数据状态。",[21,1503,1504],{"id":1504},"最后",[10,1506,1507],{},"从编程的角度来说，Schema 也像是我们自己的「语言」，编写这种语言的过程就是通过 FusionX 进行开发的过程。同样地，执行这种「语言」，也需要能够把语言转换成浏览器可以执行的 JS、HTML 和 CSS。在上面展示的 FusionX 的构成图中，其实就是一个「使用开发环境编写了编程语言，然后由解释器将其转换成可执行程序」的过程。",[10,1509,1510],{},"如果再进一步想，在计算机领域，最初的编程是通过汇编语言进行的。后来，人们采用高级语言编程。现在，人们可以使用低代码工具进行编程，刚才我们说到 Schema 其实就相当于编程语言。可以预见的未来，人们还会通过向 AI 智能体发出指令的方式来编程，那么自然语言其实也可以被看做编程语言。",[10,1512,1513,1514,43,1517,1520],{},"编程这个活动所使用的语言、开发工具和环境在发生演变，但编程作为一项活动不会消失。就像会计师始终存在，只不过所用的工具由算盘、计算器变成了计算机、财务一体化软件和 AI 智能体。作为工程师的我们，应当拥抱新的概念，并且——如果它有利于实现",[38,1515,1516],{},"降本增效",[38,1518,1519],{},"为角色赋能","的目标——积极地应用它、塑造它。",[1522,1523,1524],"style",{},"html pre.shiki code .sLo_3, html code.shiki .sLo_3{--shiki-default:#EEF0F9}html pre.shiki code .sb16X, html code.shiki .sb16X{--shiki-default:#4BF3C8}html pre.shiki code .se2J0, html code.shiki .se2J0{--shiki-default:#FFD493}html pre.shiki code .sy89t, html code.shiki .sy89t{--shiki-default:#EEF0F98F;--shiki-default-font-style:italic}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html pre.shiki code .sqF6k, html code.shiki .sqF6k{--shiki-default:#54B9FF}html pre.shiki code .stHQG, html code.shiki .stHQG{--shiki-default:#00DAEF}html pre.shiki code .s8HWQ, html code.shiki .s8HWQ{--shiki-default:#ACAFFF}html pre.shiki code .sZHg5, html code.shiki .sZHg5{--shiki-default:#54B9FF;--shiki-default-font-style:italic}html pre.shiki code .smONe, html code.shiki .smONe{--shiki-default:#4BF3C8;--shiki-default-font-style:italic}",{"title":172,"searchDepth":187,"depth":187,"links":1526},[1527,1528,1533,1536,1540,1545],{"id":23,"depth":187,"text":24},{"id":94,"depth":187,"text":95,"children":1529},[1530,1531,1532],{"id":126,"depth":208,"text":127},{"id":700,"depth":208,"text":700},{"id":733,"depth":208,"text":734},{"id":754,"depth":187,"text":755,"children":1534},[1535],{"id":796,"depth":208,"text":797},{"id":1357,"depth":187,"text":1358,"children":1537},[1538,1539],{"id":1364,"depth":208,"text":1364},{"id":1422,"depth":208,"text":1422},{"id":1446,"depth":187,"text":1447,"children":1541},[1542,1543,1544],{"id":1453,"depth":208,"text":1453},{"id":1486,"depth":208,"text":1486},{"id":1492,"depth":208,"text":1492},{"id":1504,"depth":187,"text":1504},"2025.07.07","md","摘录和整理自内部分享会中的发言，关于在构建低代码平台核心引擎过程中的感想",{},"\u002Fwriting\u002Ffusionx",{"title":5,"description":172},"writing\u002Ffusionx",[1554,1555],"Low Code","Engineering","ZtokLTT0l63GY5f4dBy6aOkFvJlWOgKTNivjQBwCFm8",1774950409695]