Help with custom module output

[Hyperbytes]

Thanks Ken

exports.tester = function () {

    return {status: 100}
}

but still not returning anything

[Hyperbytes]

Hate to tag people but can either of you help?
@George @JonL

[sid]

@Hyperbytes

defaultValue: true

The problem is default output as TRUE. Set it to false, and it should work with the way Ken has proposed.
And, the NAME input is compulsory. You are missing that.

{ name: 'actionName', optionName: 'name', title: 'Name', type: 'text', required: true, defaultValue: ''},

I have tested this just now, and it works with above changes.

Looks like a bug.

I have used names like “brian_tester” or “statuses” instead of generic words like “test” & “status”, as they might conflict with Wappler’s code - never know.

[JonL]

@sid is right.

The problem is how the SC json file is being built from the hjson.

If you open your SC file in editor you should see something like this:

{
    "name": "tester",
    "module": "tester",
    "action": "tester",
    "options": {},
    "output": true
}

But I’m pretty sure your name will be empty and output won’t be there for the reasons @sid mentions.

If you wan’t to change the default value for the output in the UI you need to use initValue

{ name: 'output', optionName: 'output', title: 'Output', initValue: true, defaultValue: false, type: 'boolean'}

[Hyperbytes]

Thanks @sid but already tried the default thing , that’s when i noticed the output flag bug I reported, no success

@sid

And, the NAME input is compulsory. You are missing that.

Sorry Sid, not following you on that, can you expand on it as to where i need that?

I have “name” in dataScheme for output

The module has no inputs so I only have “output” as an item in properties

Where is that line missing?

[JonL]

@Hyperbytes

Where is that line missing?

A variable called name

{ name: ‘name’, optionName: ‘name’, title: ‘Name’, type: ‘text’, required: true, defaultValue: ‘name’, help: ‘Help text’},

[Hyperbytes]

Thanks @JonL yet again but i already changed the default to false without success

[JonL]

Once the hjson is corrected. Remove the step in the workflow and add it again so the SC json file is generated again on save.

[JonL]

@George how about a dropdown somewhere in the UI(Extensions Manager?) to create custom modules/formatters/routes that creates the folders, files and adds some boilerplate to the js and hjson files with commented code like what lines are mandatory, link to docs, etc

[Hyperbytes]

Firstly thanks for putting up with my stupidity on this

I amended the hjson to include

I now get an output which is great

But i also see "name in the UI which i don’t want

How can i hide it?

[JonL]

I think you can’t.

[sid]

@Hyperbytes

How can i hide it?

You can try to put a default value there… and then use a non-existent input as condition for visibility?
See show/hide options.

Wappler Extensibility - Writing Custom Modules and Formatters for Server Connect

Wappler opens up its extensibility powers! Now you can define your own custom modules and formatters for Server Connect. You can write your own custom code but also provide a UI definition of your extensions so they integrate directly visually in Wappler! Writing Extensions for Server Connect Folder Structure All extensions files are placed in your project folder under the following folders: for modules: extensions/server_connect/modules for formatters extensions/server_connect/forma…

[Hyperbytes]

So i cant have an output unless there is an input?
Seems a bit bizarre for a module?

[Hyperbytes]

Thanks again @sid,
Tried all variations of

hide:[], hide:['condition'], and show[] & initDisplay: 'none'

equivalents with no success, guessing they apply specifically to dropdowns.
Need a break from this

[sid]

Using show: ['actionName'] in option property, I was able to hide the name input by default, but as soon as I enabled output, it would show the name input.

I think it is specifically designed for dropdown, as you say.

And the name input does not show default value either. So I think you will have to live with the name input there.

[Hyperbytes]

Huge thanks @sid, i will live with this for the moment and hopefully @George can look at how to/ enabling this facility when he gets time but beta to production has to be the priority at present for the team.
At least i know i am not going completely crazy (just partially)

[sid]

The name is actually required, and cannot be removed.
When you want to use the custom modules’s output, in steps below, only way to do it is using the name.
So something like name1.status will give you 100. Without the “name” part, you cannot use that step’s outputs.
And this same name is used when actually outputting the value to client side: {"name1":{"status":"100"}}
Hope this makes sense.

[Hyperbytes]

Yes, I see that. The output is the value_of_name.dataScheme_name

So if i enter “test” as the value of name then the output is test.status
So i can fix the value with defaultvalue but really want to hide the input box to make that static
Learned a lot more today about custom modules so it’s a good day anyway

[sid]

@Hyperbytes

but really want to hide the input box to make that static

That would be helpful if you have just one of such steps in the SA.
But if you have many in the same SA, the value of the “name” will keep overriding itself after each step.

[Hyperbytes]

Fair comment. Guess I was very focused on my particular use case where overwrite would be the correct result.