GetBNFAsync Method
Overloads
| GetBNFAsync(BNFType) |
Gets the current Backus-Naur Form (BNF) grammar of the Qlik engine scripting language. The BNF rules define the syntax for the script statements and the script or chart functions. In the Qlik engine BNF grammar, a token is a string of one or more characters that is significant as a group. For example, a token could be a function name, a number, a letter, a parenthesis, and so on. |
|
| GetBNFAsync(AsyncHandle, BNFType) |
Gets the current Backus-Naur Form (BNF) grammar of the Qlik engine scripting language. The BNF rules define the syntax for the script statements and the script or chart functions. In the Qlik engine BNF grammar, a token is a string of one or more characters that is significant as a group. For example, a token could be a function name, a number, a letter, a parenthesis, and so on. |
|
| GetBNFAsync<T>(AsyncHandle, Func<Response, T>, BNFType) |
Gets the current Backus-Naur Form (BNF) grammar of the Qlik engine scripting language. The BNF rules define the syntax for the script statements and the script or chart functions. In the Qlik engine BNF grammar, a token is a string of one or more characters that is significant as a group. For example, a token could be a function name, a number, a letter, a parenthesis, and so on. |
GetBNFAsync(BNFType)
Gets the current Backus-Naur Form (BNF) grammar of the Qlik engine scripting language. The BNF rules define the syntax for the script statements and the script or chart functions.
In the Qlik engine BNF grammar, a token is a string of one or more characters that is significant as a group. For example, a token could be a function name, a number, a letter, a parenthesis, and so on.
Declaration
[Obsolete("Use the _GetBaseBNF_ method instead")]
Task<IEnumerable<BNFDef>> GetBNFAsync([QixName("qBnfType")] BNFType bnfType)
Parameters
| Type | Name | Description |
|---|---|---|
| BNFType | bnfType |
Returns a set of rules defining the syntax for:
|
Returns
| Type | Description |
|---|---|
| System.Threading.Tasks.Task<System.Collections.Generic.IEnumerable<BNFDef>> |
GetBNFAsync(AsyncHandle, BNFType)
Gets the current Backus-Naur Form (BNF) grammar of the Qlik engine scripting language. The BNF rules define the syntax for the script statements and the script or chart functions.
In the Qlik engine BNF grammar, a token is a string of one or more characters that is significant as a group. For example, a token could be a function name, a number, a letter, a parenthesis, and so on.
Declaration
[Obsolete("Use the _GetBaseBNF_ method instead")]
Task<IEnumerable<BNFDef>> GetBNFAsync(AsyncHandle asyncHandle, [QixName("qBnfType")] BNFType bnfType)
Parameters
| Type | Name | Description |
|---|---|---|
| AsyncHandle | asyncHandle |
Handle to asynchronous method request |
| BNFType | bnfType |
Returns a set of rules defining the syntax for:
|
Returns
| Type | Description |
|---|---|
| System.Threading.Tasks.Task<System.Collections.Generic.IEnumerable<BNFDef>> |
GetBNFAsync<T>(AsyncHandle, Func<Response, T>, BNFType)
Gets the current Backus-Naur Form (BNF) grammar of the Qlik engine scripting language. The BNF rules define the syntax for the script statements and the script or chart functions.
In the Qlik engine BNF grammar, a token is a string of one or more characters that is significant as a group. For example, a token could be a function name, a number, a letter, a parenthesis, and so on.
Declaration
[Obsolete("Use the _GetBaseBNF_ method instead")]
Task<T> GetBNFAsync<T>(AsyncHandle asyncHandle, Func<Response, T> onResult, [QixName("qBnfType")] BNFType bnfType)
Parameters
| Type | Name | Description |
|---|---|---|
| AsyncHandle | asyncHandle |
Handle to asynchronous method request |
| System.Func<Response, T> | onResult |
Continuation function |
| BNFType | bnfType |
Returns a set of rules defining the syntax for:
|
Returns
| Type | Description |
|---|---|
| System.Threading.Tasks.Task<T> |
Type Parameters
| Name | Description |
|---|---|
| T |
Did this page help you?
If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!