Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Adding a non valid bond type on a property generates an exception #2

Open
pabloalonso opened this issue Mar 23, 2017 · 0 comments

Comments

@pabloalonso
Copy link
Contributor

Adding a property like:
{ "label": "Value", "name": "value", "type": "text", "defaultValue": "This is the initial value", "bond": "anyValue" }
generates the following output trying to deploy

`[17:04:23] Using gulpfile C:\Proyectos#DESARROLLO\ContribWidgets\contribution-widgets\gulpfile.js
[17:04:23] Starting 'deploy'...
[17:04:23] Starting 'build'...
[17:04:24] Finished 'deploy' after 53 ms
[17:04:24] Finished 'build' after 385 ms
[17:04:24] Starting 'zip'...
[17:04:24] Finished 'zip' after 161 ms
[17:04:24] Starting 'deploy:single'...
C:\Proyectos#DESARROLLO\ContribWidgets\contribution-widgets\script\deploy.js:15
gutil.log(gutil.colors.red('Failed to deploy widget '' + gutil.colors.cyan(widget.element.name) + '' reason :' + widget.status));
^

TypeError: Cannot read property 'name' of undefined
at logDeploymentResult (C:\Proyectos#DESARROLLO\ContribWidgets\contribution-widgets\script\deploy.js:15:95)
at Request._callback (C:\Proyectos#DESARROLLO\ContribWidgets\contribution-widgets\script\deploy.js:38:7)
at Request.self.callback (C:\Proyectos#DESARROLLO\ContribWidgets\contribution-widgets\node_modules\request\request.js:198:22)
at emitTwo (events.js:106:13)
at Request.emit (events.js:191:7)
at Request. (C:\Proyectos#DESARROLLO\ContribWidgets\contribution-widgets\node_modules\request\request.js:1063:14)
at emitOne (events.js:101:20)
at Request.emit (events.js:188:7)
at IncomingMessage. (C:\Proyectos#DESARROLLO\ContribWidgets\contribution-widgets\node_modules\request\request.js:1009:12)
at emitNone (events.js:91:20)
at IncomingMessage.emit (events.js:185:7)
at endReadableNT (_stream_readable.js:974:12)
at _combinedTickCallback (internal/process/next_tick.js:80:11)
at process._tickCallback (internal/process/next_tick.js:104:9)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] deploy: gulp deploy "--widget" "customMultiSelection" "--host" "http://localhost:26190/designer" "--watch" "--force"
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] deploy script 'gulp deploy "--widget" "customMultiSelection" "--host" "http://localhost:26190/designer" "--watch" "--force"'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the widget-seed package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! gulp deploy "--widget" "customMultiSelection" "--host" "http://localhost:26190/designer" "--watch" "--force"
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs widget-seed
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls widget-seed
npm ERR! There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\pablo\AppData\Roaming\npm-cache_logs\2017-03-23T16_04_24_662Z-debug.log`

@pabloalonso pabloalonso changed the title Adding a non valid bond type on a property generates an exception [Bug] Adding a non valid bond type on a property generates an exception Mar 23, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant