No docs, but it’s available. It is the grid control.
@sid implemented it in a custom extension. Check its source code.
No docs, but it’s available. It is the grid control.
@sid implemented it in a custom extension. Check its source code.
Nooo… You are just too late!!! Would’ve saved me the last 30 min of making my own object with static options…
Thanks Jon will see if I can get it working
Got it working @JonL - it was easier than expected for once…
Edit:
For future readers, this is my example code:
{ name: 'headers', optionName: 'headers', key: 'name', keyValue: 'value',
title: 'Headers', type: 'grid',defaultValue: {}, serverDataBindings: true,
columns: [
{ field: 'name', caption: 'Name', size: '50%', editable: {type: 'text'} },
{ field: 'value', caption: 'Value', size: '50%', allowJson: true, editable: {type: 'datapicker'} },
],
newRecord: { name: '', value: ''}
}
Is it possible to:
That is currently not possible. The option groups have max width and float next to each other depending on the available space. Will see if we can improve that in general in the future.
that would be awesome! so much scope for better use of space!
We just added support for the on demand node modules installation, so now you can add those to the Hjson as well,
@George at what point do the required modules get installed?
When you add a step with an action for the module to a SC flow.
And if you need to pass an object as a variable? Is there no such option now?
Not behind my pc now but I think I’m passing objects trough the text field without a problem, otherwise you can stringify and then parse it in the module
The 1st option works
Just bumping this doc as it is now updated to allow extension builders also to specify PHP modules to be specified that will be auto installed with PHP composer now available in Wappler 5.6