Improve preferences building, and generate the preferences_schema.json file for the Chromium addon#20603
Conversation
|
/botio unittest |
From: Bot.io (Linux m4)ReceivedCommand cmd_unittest from @Snuffleupagus received. Current queue size: 0 Live output at: http://54.241.84.105:8877/0ddb7883bcc9010/output.txt |
From: Bot.io (Windows)ReceivedCommand cmd_unittest from @Snuffleupagus received. Current queue size: 1 Live output at: http://54.193.163.58:8877/74448fcc3db800c/output.txt |
From: Bot.io (Linux m4)SuccessFull output at http://54.241.84.105:8877/0ddb7883bcc9010/output.txt Total script time: 2.62 mins
|
From: Bot.io (Windows)FailedFull output at http://54.193.163.58:8877/74448fcc3db800c/output.txt Total script time: 8.82 mins
|
|
/botio-linux integrationtest |
From: Bot.io (Linux m4)ReceivedCommand cmd_integrationtest from @Snuffleupagus received. Current queue size: 0 Live output at: http://54.241.84.105:8877/a973a1c90de7e58/output.txt |
From: Bot.io (Linux m4)SuccessFull output at http://54.241.84.105:8877/a973a1c90de7e58/output.txt Total script time: 21.72 mins
|
…during building This avoids the hassle of having to manually update that file when adding/modifying preferences in the viewer. Updating the preferences-metadata should now only be something that the Chromium addon maintainer has to do.
This is a left-over from before the introduction of `AppOptions`, but is no longer necessary now.
…ly for all relevant build-targets Given that previous patches reduced that number of build-targets running this code, ensure that it's still tested sufficiently.
This really isn't necessary, and it's just a left-over from before the code was moved into the current file. Also, spotted during rebasing, use the existing "locale" hash-parameter in integration-tests rather than adding a duplicate one for testing.
Snuffleupagus
force-pushed
the
createChromiumPrefsSchema
branch
from
5f04a09 to
1370950
Compare
3 participants
This avoids the hassle of having to manually update that file when adding/modifying preferences in the viewer.
Updating the preferences-metadata should now only be something that the Chromium addon maintainer has to do.