@ClientCallable should support return values
See original GitHub issueGiven
@ClientCallable
public void removeTodo(int index, String text) {
...
}
I really want to be able to provide information back to the client about whether the item was deleted, or if e.g. an optimistic locking / merge conflict occurred. The logical way would be
@ClientCallable
public boolean removeTodo(int index, String text) {
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
client callable script include for field value - ServiceNow
In client callable script include function use GlideRecord query on table 'Maintain' and get the no of records assigned to passed parameter ...
Read more >Remote Procedure Calls | Manipulating DOM with Element API
If the return value is a JavaScript Promise , then a return value will be sent to the server only when the Promise...
Read more >Client & Server Code in One UI Action - ServiceNow Guru
//Get the values from the Incident Table so we can write-back to it. Done in server side code now. var comments = g_form.getValue('comments');...
Read more >AutomationPeer.GetFlowsToCore Method (Microsoft.UI.Xaml ...
... an associated UI Automation client-callable method. You can override any of the "Core" methods to return alternative values in a custom automation...
Read more >Vaadin 18 | Need to pass a message from client to server ...
And then the <vaadin-horizontal-layout> instance would get the $server. ... ClientCallable; import com.vaadin.flow.component.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
On the client side, one quite obvious API approach would be that
element.$server.foo(1, "foo")
returns aPromise
.This feature barely missed the train for Vaadin 14.1. It will be in Vaadin 14.2 that will be released at some point in the beginning of next year.