To add contract to the builder, I've darkened the top navbar (primary color). I've also added preview and a settings icon, as well as removing borders from nav items.
* new binding...
- state manager
- one store per screen
- not passing
* client lib binding - tests passing
* binding fully working again post stateManager
* bugfix with button component
* Control flow ("code") now working, tests passing
* Events List now reading from component definition
* fix to button.svelte - missing props._children
* typo - screens not being sent to page save
* removed children arg from hydrateChildren (n/a)
* initialiseChildren does not rerender unless forced
* removed derivatives of initialiseChildren
* renamed initialiseChildren > attachChildren
* standard-components - refactoring
div now container
H1, h2... etc now Heading with type
Select now takes option as _children
* loads of bug fixing
* safe props creation
anytime props are loaded,
we make sure they conform to the components props definition
ixing broken tests on client
typo in buildPage.js
fixing some server tests
local datastore uses fs-extra remove, not rmdir
client - loadBudibase - no longer destructuring arg
updated publishdev script for client (reads apps)
prettier fix
some little bug fixes
bugfix - set screens to empty array when falsy
typo in template page.json
replaced "Shard Factor" for "Estimated Count"
* refactoring server for screens & page layout restructure
* Disable API calls, UI placeholders.
* buildPropsHierarchy is gone & screen has url
* Recent changes.
* router
* router
* updated git-ignore to reinclude server/utilities/builder
* modified cli - budi new create new file structure
* Fix uuid import.
* prettier fixes
* prettier fixes
* prettier fixes
* page/screen restructure.. broken tests
* all tests passing at last
* screen routing tests
* Working screen editor and preview.
* Render page previews to the screen.
* Key input lists to ensure new array references when updating styles.
* Ensure the iframe html and body fills the container.
* Save screens via the API.
* Get all save APIs almost working.
* Write pages.json to disk.
* Use correct API endpoint for saving styles.
* Differentiate between saving properties of screens and pages.
* Add required fields to default pages layouts.
* Add _css default property to newly created screens.
* Add default code property.
* page layout / screens - app output
* backend and fronend save seperately
Co-authored-by: pngwn <pnda007@gmail.com>
Martin McKeaveney
Michael Shanks
Joe
Martin McKeaveney