[Project Template] Web API Server NEXT

1. Multiline body format
2. Generate help without run debug
3. Custom property or Override auto generated property (e.g method name doesn't need to start with Get)

aeric said:

Some ideas:

1. Multiline body format
2. Generate help without run debug
3. Custom property or Override auto generated property (e.g method name doesn't need to start with Get)

Click to expand...

1. Some adjustments on the handling of XML format response in frontend and help page
2. Demonstrate usage of VerboseMode in WebApiUtils v4 to replace SimpleResponse in WebApiUtils v3.
3. Demonstrate support for XML format response in WebApiUtils v4

' Main module
Private Sub Configurable
    conf.SimpleResponse.Enable = True
End Sub

' Initialize handler
Public Sub Initialize
    HRM.Initialize
    HRM.SimpleResponse = Main.conf.SimpleResponse
End Sub

' Main module
Private Sub Configurable
    conf.VerboseMode = False
End Sub

' Initialize handler
Public Sub Initialize
    HRM.Initialize
    HRM.VerboseMode = Main.conf.VerboseMode
End Sub

aeric said:

no major changes in Web API Server v4 compared to v3

Click to expand...

aeric said:

smart

Click to expand...

aeric said:

There is a Utility modul where it's primary use is to generate 3 javascript files during compilation for the front end and help page interactivity.

This modul is actually not required if you are not using the front end and help page.

For the past few weeks, for the sake of demonstrating the features of the new framework and WebApiUtils, I have taken so much time to refine the module to produce perfectly structure javascript so that it can be readable when using text editor.

I also tried to refactor, minimize the file size of the generated js files and simplified the code in Utility module.

It is a challenging task as I need to take consideration of all possible combination of server configuration and HttpResponseMessage properties.

The js files will be dynamically generated base on:
1. Content Type (XML or JSON)
2. Verbose (with or without the "smart" keys)
3. Ordered keys or non-ordered keys
4. Http verb (get, post, put, delete)
Note: Post verb can store access token if exist
5. Using custom alias names for "smart" keys
6. Custom XML keys for root and item

Click to expand...

Mashiane said:

Build a wizard, Mr Wizard.

Step 1: Select the DB... (SQLite / MySQL)
Step 2: Select the tables to produce an API for
Step 3: For each selected table, select the fields you want to use on the API.
Step 4: Generate the API code.
Step 5: b4x coder creates a project from your Web API Template
Step 6: Plug in your Wizard Generated Code
Step 7: Run your app.



PS: That way we won't have to learn and understand your code at all.. (Joking of course)

Click to expand...