quix
quix copied to clipboard
faild to add note
@qianshengzj , can you please share the value of window.quixConfig
?
same issue. I have checked window.quixConfig
and I do not know why there are 2 different presto modules. If it's the reason how to fix this? I just clone the repo and run docker compose up
. Probably there is something wrong with default setup.
{
"modules": [
{
"id": "presto",
"name": "presto",
"components": {
"db": {},
"note": {}
},
"engine": "presto",
"syntax": "presto"
},
{
"id": "presto",
"name": "presto",
"components": {
"db": {},
"note": {}
},
"engine": "presto",
"syntax": "presto"
}
],
"auth": {
"googleClientId": ""
},
"clientTopology": {
"executeBaseUrl": "localhost:8081",
"staticsBaseUrl": "/",
"apiBasePath": ""
},
"mode": {
"debug": false,
"demo": false
}
}
I repeat the same behaviour here
The root problem might be the same for this issue https://github.com/wix/quix/issues/348
Indeed, I have the same error in the console when i click on the Note
dropdown or the DB Explorer
drop down:
Error: [ngRepeat:dupes] Duplicates in a repeater are not allowed. Use 'track by' expression to specify unique keys. Repeater: option in buffer, Duplicate key: string:presto, Duplicate value: presto
https://errors.angularjs.org/1.8.2/ngRepeat/dupes?p0=option%20in%20buffer&p1=string%3Apresto&p2=presto
I also tried to us two differents modules : presto and postgresql. This is what I have in the console:
window.quixConfig
Object { modules: (4) […], auth: {…}, clientTopology: {…}, mode: {…} }
auth: Object { googleClientId: "" }
clientTopology: Object { executeBaseUrl: "localhost:8081", staticsBaseUrl: "/", apiBasePath: "" }
mode: Object { debug: false, demo: false }
modules: Array(4) [ {…}, {…}, {…}, … ]
0: Object { id: "presto", name: "presto", engine: "presto", … }
1: Object { id: "postgresql", name: "postgresql", engine: "jdbc", … }
2: Object { id: "presto", name: "presto", engine: "presto", … }
3: Object { id: "postgresql", name: "postgresql", engine: "jdbc", … }
<prototype>: Array []
<prototype>: Object { … }
It seems that modules are loaded twice in the frontend
@0inp thanks for the answer. I did not check the code yet, but I guess your assumption is valid about loading twice. I will try to check and in case I have time to check and find something will create PR or at least share it here.