Function "to" is accessing types wrong and does not work #32597
Assignees
Labels
blocker
bug
Fixes for quality problems that affect the customer experience
Feature:Canvas
PR sent
regression
Team:Presentation
Presentation Team for Dashboard, Input Controls, and Canvas
Team:Visualizations
Visualization editors, elastic-charts and infrastructure
v6.7.0
v7.0.0
Projects
Comments
w33ble
added
bug
|
Pinging @elastic/kibana-canvas |
|
Pinging @elastic/kibana-app |
w33ble
changed the title
w33ble
added a commit
that referenced
this issue
Mar 8, 2019
…unctions (#32600) Closes #32356 This PR fixes two issues. The first there was an issue filed, #32356: - Show non-Boom errors instead of asking users to look at server logs - Also write the error to the server when asking them to look there ### Before  *If the function failed for some reason, this is all you'd ever see* ### After  *Errors are shown to the user*  *Code errors bubble up correctly as well* --- The other I didn't bother opening an issue for: - Fixes issue where functions that return `null` produce an error message - `null` is a valid thing to return, it's only `undefined` that causes a problem - This was only a problem for server functions that return `null` (currently, none of them do) - Introduced in #31298 - Discovered when I ran into casting problems (see #32597) ### Before  ### After 
w33ble
added a commit
to w33ble/kibana
that referenced
this issue
Mar 8, 2019
…unctions (elastic#32600) Closes elastic#32356 This PR fixes two issues. The first there was an issue filed, elastic#32356: - Show non-Boom errors instead of asking users to look at server logs - Also write the error to the server when asking them to look there ### Before  *If the function failed for some reason, this is all you'd ever see* ### After  *Errors are shown to the user*  *Code errors bubble up correctly as well* --- The other I didn't bother opening an issue for: - Fixes issue where functions that return `null` produce an error message - `null` is a valid thing to return, it's only `undefined` that causes a problem - This was only a problem for server functions that return `null` (currently, none of them do) - Introduced in elastic#31298 - Discovered when I ran into casting problems (see elastic#32597) ### Before  ### After 
w33ble
added a commit
to w33ble/kibana
that referenced
this issue
Mar 8, 2019
…unctions (elastic#32600) Closes elastic#32356 This PR fixes two issues. The first there was an issue filed, elastic#32356: - Show non-Boom errors instead of asking users to look at server logs - Also write the error to the server when asking them to look there  *If the function failed for some reason, this is all you'd ever see*  *Errors are shown to the user*  *Code errors bubble up correctly as well* --- The other I didn't bother opening an issue for: - Fixes issue where functions that return `null` produce an error message - `null` is a valid thing to return, it's only `undefined` that causes a problem - This was only a problem for server functions that return `null` (currently, none of them do) - Introduced in elastic#31298 - Discovered when I ran into casting problems (see elastic#32597)  
w33ble
added a commit
to w33ble/kibana
that referenced
this issue
Mar 8, 2019
…unctions (elastic#32600) Closes elastic#32356 This PR fixes two issues. The first there was an issue filed, elastic#32356: - Show non-Boom errors instead of asking users to look at server logs - Also write the error to the server when asking them to look there  *If the function failed for some reason, this is all you'd ever see*  *Errors are shown to the user*  *Code errors bubble up correctly as well* --- The other I didn't bother opening an issue for: - Fixes issue where functions that return `null` produce an error message - `null` is a valid thing to return, it's only `undefined` that causes a problem - This was only a problem for server functions that return `null` (currently, none of them do) - Introduced in elastic#31298 - Discovered when I ran into casting problems (see elastic#32597)  
w33ble
added a commit
that referenced
this issue
Mar 8, 2019
…unctions (#32600) (#32797) Closes #32356 This PR fixes two issues. The first there was an issue filed, #32356: - Show non-Boom errors instead of asking users to look at server logs - Also write the error to the server when asking them to look there  *If the function failed for some reason, this is all you'd ever see*  *Errors are shown to the user*  *Code errors bubble up correctly as well* --- The other I didn't bother opening an issue for: - Fixes issue where functions that return `null` produce an error message - `null` is a valid thing to return, it's only `undefined` that causes a problem - This was only a problem for server functions that return `null` (currently, none of them do) - Introduced in #31298 - Discovered when I ran into casting problems (see #32597)  
w33ble
added a commit
that referenced
this issue
Mar 8, 2019
…unctions (#32600) (#32792) Closes #32356 This PR fixes two issues. The first there was an issue filed, #32356: - Show non-Boom errors instead of asking users to look at server logs - Also write the error to the server when asking them to look there ### Before  *If the function failed for some reason, this is all you'd ever see* ### After  *Errors are shown to the user*  *Code errors bubble up correctly as well* --- The other I didn't bother opening an issue for: - Fixes issue where functions that return `null` produce an error message - `null` is a valid thing to return, it's only `undefined` that causes a problem - This was only a problem for server functions that return `null` (currently, none of them do) - Introduced in #31298 - Discovered when I ran into casting problems (see #32597) ### Before  ### After 
w33ble
added a commit
that referenced
this issue
Mar 8, 2019
…unctions (#32600) (#32794) Closes #32356 This PR fixes two issues. The first there was an issue filed, #32356: - Show non-Boom errors instead of asking users to look at server logs - Also write the error to the server when asking them to look there  *If the function failed for some reason, this is all you'd ever see*  *Errors are shown to the user*  *Code errors bubble up correctly as well* --- The other I didn't bother opening an issue for: - Fixes issue where functions that return `null` produce an error message - `null` is a valid thing to return, it's only `undefined` that causes a problem - This was only a problem for server functions that return `null` (currently, none of them do) - Introduced in #31298 - Discovered when I ran into casting problems (see #32597)  
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Kibana version: 6.7+
Describe the bug:
When doing any casting with the
tofunction, nothing works because the function tries to grab types from handlers, which is wrong. Types need to be accessed from@kbn/interpreternow.So the value of types is undefined, and you end up with this error:
Steps to reproduce:
towith a server function, likedemodata | to type="null"The text was updated successfully, but these errors were encountered: