gnome-shell/subprojects/extensions-tool/src
Chuck d1f87ca115 extension-tool: Don't treat missing .js handler as error
After creating a new extension, we try to open the main source
file with the default handler, which fails when there is none.

But given that the extension was created successfully, don't treat
a missing handler as failure, and print the path to the new extension
instead.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/905
2019-12-20 14:11:03 +00:00
..
template extensions-tool: Move to a subproject 2019-12-18 19:13:24 +00:00
command-create.c extension-tool: Don't treat missing .js handler as error 2019-12-20 14:11:03 +00:00
command-disable.c extensions-tool: Move to a subproject 2019-12-18 19:13:24 +00:00
command-enable.c extensions-tool: Move to a subproject 2019-12-18 19:13:24 +00:00
command-info.c extensions-tool: Move to a subproject 2019-12-18 19:13:24 +00:00
command-install.c extensions-tool: Move to a subproject 2019-12-18 19:13:24 +00:00
command-list.c extensions-tool: Move to a subproject 2019-12-18 19:13:24 +00:00
command-pack.c extensions-tool: Move to a subproject 2019-12-18 19:13:24 +00:00
command-prefs.c extensions-tool: Move to a subproject 2019-12-18 19:13:24 +00:00
command-reset.c extensions-tool: Move to a subproject 2019-12-18 19:13:24 +00:00
command-uninstall.c extensions-tool: Move to a subproject 2019-12-18 19:13:24 +00:00
commands.h extensions-tool: Move to a subproject 2019-12-18 19:13:24 +00:00
common.h extensions-tool: Move to a subproject 2019-12-18 19:13:24 +00:00
gnome-extensions-tool.gresource.xml extensions-tool: Move to a subproject 2019-12-18 19:13:24 +00:00
main.c extensions-tool: Move to a subproject 2019-12-18 19:13:24 +00:00
meson.build extensions-tool: Move to a subproject 2019-12-18 19:13:24 +00:00