budibase/packages/client
Joe f417c2d8a4
Joe's lab day minor updates (#12944)
* Change default button type to CTA

- change default button type to CTA
- change ordering of types/variants

* Fix layout shift within portal

Within the portal, when navigating from screen to screen, there's a slight layout shift caused by the scrollbar. This is a small fix.

* row/column icons change

The current row/column icons for positioning components are confusing. I believe these icons are easier to understand.

* Fix for horizontal scrollbar showing

When adding/removing actions within automations, the horizontal scrollbar flashes. Fix.

* Title change for Upload data

Upload data is not wrong, but it's best to be explicit.

* Increase size of upgrade button

* small fix for the styling inconsistency

* Dianostics padding fix

* lint fix

* update account-portal

* update icons

---------

Co-authored-by: melohagan <101575380+melohagan@users.noreply.github.com>
Co-authored-by: Mel O'Hagan <mel@budibase.com>
2024-02-21 13:28:35 +00:00
..
src Joe's lab day minor updates (#12944) 2024-02-21 13:28:35 +00:00
.gitignore
.npmignore
LICENSE
README.md
manifest.json Joe's lab day minor updates (#12944) 2024-02-21 13:28:35 +00:00
package.json Remove unused regexparam 2024-01-08 14:06:54 +01:00
rollup.config.js Fix build 2023-08-02 00:25:24 +02:00

README.md

Manifest

The manifest.json file exports the definitions of all components available in this version of the client library. The manifest is used by the builder to correctly display components and their settings, and know how to correctly interact with them.

Component Definitions

The object key is the name of the component, as exported by index.js.

  • name - the name displayed in the builder
  • description - not currently used
  • icon - the icon displayed in the builder
  • hasChildren - whether the component accepts children or not
  • styleable - whether the component accepts design props or not
  • dataProvider - whether the component provides a data context or not
  • bindable - whether the components provides a bindable value or not
  • settings - array of settings displayed in the builder

Settings Definitions

The type field in each setting is used by the builder to know which component to use to display the setting, so it's important that this field is correct. The valid options are:

  • text - A text field
  • select - A select dropdown. Accompany these with an options field to provide options
  • datasource - A datasource (e.g. a table or a view)
  • boolean - A boolean field
  • number - A numeric text field
  • detailURL - A URL to a page which displays details about a row. Exclusively used for grids which link to row details.

The available fields in each setting definition are:

  • type - the type of field which determines which component the builder will use to display the setting
  • key - the key of this setting in the component
  • label - the label displayed in the builder
  • defaultValue - the default value of the setting
  • placeholder - the placeholder for the setting