Query post-transformation, autocompletion support
See original GitHub issueCurrently it’s unintuitive to build a post-transformation. The code editor doesn’t help the user at all with autocomplete. One possible solution could be to, instead of expecting a function expression, we expect a function body, we can the supply data
in the globalScope
property of the editor to get autocomplete for free.
return data;
instead of
(data) => {
return data;
}
@bharatkashyap what do you think?
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:5 (5 by maintainers)
Top Results From Across the Web
How To Use Autocomplete Feature in Query Tool - EDB
To use autocomplete, begin typing your query; when you would like the query editor to suggest object names or commands that might be...
Read more >Query Autocomplete | Places API - Google Developers
The Query Autocomplete service can be used to provide a query prediction for text-based geographic searches, by returning suggested queries as you type....
Read more >Use Autocompletions to suggest searches quickly
Use Autocompletions to suggest searches quickly. Autocompletions shows users useful queries while they are typing. For example, with autocompletions enabled, ...
Read more >Deep Learning Methods for Query Auto Completion - Microsoft
Query Auto Completion (QAC) aims to help users reach their search intent faster and is a gateway to search for users.
Read more >Supporting typeahead autocomplete with ElasticSearch
You can use Edge NGram based analyzer, see http://www.elasticsearch.org/guide/reference/index-modules/analysis/edgengram-tokenizer.html.
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 Free
Top 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
You can add
diagnosticCodesToIgnore: [1108]
undermonaco.languages.typescript.typescriptDefaults.setDiagnosticsOptions
We would however have two JSON previews on one page with the same variable
data
having different values: