hkollmann on es6ify
run es6ify again with latest bu… (compare)
hkollmann on master
fix: tangible theme table-edito… (compare)
localModules
in the compile.json without changing the schema...
I've followed up a bit on why schema validation wasn't working. There are a few issues. Firstly, the correct property banning extra keys was missing, and an obsolete one was in its place. Secondly, with the correct property there, it tries to use better-ajv-errors
but it was not properly required, so crashed when trying to generate the error. Those two problems are fixed with this patch:
Unstaged changes (2)
modified source/class/qx/tool/utils/Json.js
@@ -23,7 +23,7 @@
* *********************************************************************** */
const Ajv = require("ajv");
-const betterAjvErrors = require("better-ajv-errors");
+const betterAjvErrors = require("better-ajv-errors").default;
const fs = qx.tool.utils.Promisify.fs;
qx.Class.define("qx.tool.utils.Json", {
modified source/resource/qx/tool/schema/compile-1-0-0.json
@@ -53,7 +53,7 @@
"minItems": 1,
"items": {
"type": "object",
- "additionalItems": false,
+ "additionalProperties": false,
"required": [
"class",
"name"
The third problem is that validation is being done when running qx clean
but not when running qx compile
. I'm not sure where to look to fix that problem. I also know little about schema validation, so someone with more knowledge of it should check my work and apply a PR if appropriate.
With Qooxdoo 7, should image resources in a combined png/meta be retrieved from that combined image resource? I can some entries in the resource-db.json
, but looking at qx.$$resources
at runtime there isn't a reference to the combined image.
Here's a cut down version of the resource-db.json for the gb flag which is contained in a flags_combined.png
{
"resources": {
"plaid": {
"plaid/flags_combined.meta": {
"resourcePath": "resourcePath",
"meta": {
"plaid/icons/flags/gb.png": [
16,
11,
"png",
"plaid/flags_combined.png",
-1163,
0
]
}
},
"plaid/flags_combined.png": {
"resourcePath": "resourcePath",
"width": 3748,
"height": 11
},
"plaid/icons/flags/gb.png": {
"resourcePath": "resourcePath",
"width": 16,
"height": 11
}
}
}
}
I, we are using the last version of qooxdoo to migrate from 5.0.0 version. For now we are fine, but we find a problem with the translations of our main library. We use it in the next way:
"libraries": [
"./qxnw.6.0/trunk",
"."
],
In the compile.json and in that library we have the .po translations file. The problem is that we can't see that translations in our application as we have in the older version. Please help!!!!
jose
installed in node_modules
?
npm install
ed
npm install jose
and then qx compile
gave me this:Failed: Error: Parsing file /home/sknick/<snipped>/node_modules/jose/dist/browser/index.js: 'import' and 'export' may only appear at the top level (2:0)
/home/sknick/<snipped>/node_modules/@qooxdoo/framework/lib/compiler/index.js:55029
throw e;
export { compactDecrypt } from './jwe/compact/decrypt.js';
export { flattenedDecrypt } from './jwe/flattened/decrypt.js';
export { generalDecrypt } from './jwe/general/decrypt.js';
export { GeneralEncrypt } from './jwe/general/encrypt.js';
export { compactVerify } from './jws/compact/verify.js';
export { flattenedVerify } from './jws/flattened/verify.js';
export { generalVerify } from './jws/general/verify.js';
export { jwtVerify } from './jwt/verify.js';
export { jwtDecrypt } from './jwt/decrypt.js';
export { CompactEncrypt } from './jwe/compact/encrypt.js';
export { FlattenedEncrypt } from './jwe/flattened/encrypt.js';
export { CompactSign } from './jws/compact/sign.js';
export { FlattenedSign } from './jws/flattened/sign.js';
export { GeneralSign } from './jws/general/sign.js';
export { SignJWT } from './jwt/sign.js';
export { EncryptJWT } from './jwt/encrypt.js';
export { calculateJwkThumbprint } from './jwk/thumbprint.js';
export { EmbeddedJWK } from './jwk/embedded.js';
export { createLocalJWKSet } from './jwks/local.js';
export { createRemoteJWKSet } from './jwks/remote.js';
export { UnsecuredJWT } from './jwt/unsecured.js';
export { exportPKCS8, exportSPKI, exportJWK } from './key/export.js';
export { importSPKI, importPKCS8, importX509, importJWK } from './key/import.js';
export { decodeProtectedHeader } from './util/decode_protected_header.js';
export { decodeJwt } from './util/decode_jwt.js';
import * as errors_1 from './util/errors.js';
export { errors_1 as errors };
export { generateKeyPair } from './key/generate_key_pair.js';
export { generateSecret } from './key/generate_secret.js';
import * as base64url_1 from './util/base64url.js';
export { base64url_1 as base64url };
browserify
option that would fix it. I'll look into it. It's bundling the required file and its imports. That may be the first time an ES6 module has been included. If I can figure anything out I'll let you know (even though you won't care since you're not using that library)
?qooxdoo:load-parallel=true
async
attribute. QX6