Skip to content

Releases: makeswift/makeswift

@makeswift/runtime@0.0.13

28 May 19:01
Compare
Choose a tag to compare

Patch Changes

  • 6dd8bfb: Fix FOUC when using Style control.
  • 394afc1: Fix SSR issues with next/image and Next.js' router.

@makeswift/runtime@0.0.12

27 May 16:15
Compare
Choose a tag to compare

Patch Changes

  • 4ebe3dc: Fix snippets not updated immediately after changes
  • aa558b3: Fix snippets invoked twice
  • 936ab95: Fix scrolling doesn't work in content mode when hovering over a text block
  • 392227e: Fix font not applied when added to site

@makeswift/runtime@0.0.11

24 May 19:16
Compare
Choose a tag to compare

Patch Changes

  • 3f140f5: Change Shape control formated value property sort order.
  • e815641: Recursively serialize List control. This fixes an issue where nested types in a List control would not be serialized.
  • eefeec7: Avoid calling includes on non-string value when suppressing React warnings.
  • dd97bce: Fix Form button alignment prop not being applied
  • e703d17: Remove label from Shape control.

@makeswift/runtime@0.0.10

17 May 06:05
Compare
Choose a tag to compare

Patch Changes

  • 84c1324: Handle ESC key to change from content mode to build mode.
  • 2d3dab2: Fix if you have text selection in the builder, clicking on any of the text panel will remove the text selection bug.
  • bb78979: Fix overlay for nested global components are showing the wrong selection, making you unable to edit.

@makeswift/runtime@0.0.9

04 May 16:28
Compare
Choose a tag to compare

The last release, 0.0.8 didn't properly fix the useInsertionEffect issue. This time it's for real, though!

Patch Changes

  • f8b5b96: Fix (again) the opt-in to useInsertionEffect, making sure that transpilers will not attempt to inline the import specifier.

@makeswift/runtime@0.0.8

04 May 15:54
Compare
Choose a tag to compare

Patch Changes

  • a4006a7: Fix transpilation issue that caused useInsertionEffect to be referenced directly in import specifiers.

@makeswift/runtime@0.0.7

03 May 03:05
Compare
Choose a tag to compare

Patch Changes

  • d1dd2fa: Add new Number control.
  • 0b64822: Add new Select control.
  • 053e1cd: Improve inferred TypeScript types when registering a component.
  • 252fece: Add new Image control.
  • c76d470: Add new TextArea control.
  • ab35043: Add new Checkbox control.
  • 471766b: Add new Color control.
  • b860dde: Add new TextInput control.
  • 1e93d48: Add new List and Shape controls.

@makeswift/runtime@0.0.6

29 Apr 14:24
Compare
Choose a tag to compare

Patch Changes

  • 85c08d0: Hide scrollbar in builder mode but not in preview.
  • d06a708: Apply gutter to navigation logo
  • f27521f: Fix Text in preview mode being editable.
  • b467150: Fix social icons not sized correctly.
  • 0cb56d9: Fix bug where editing global element with Text as the root element isn't working.

@makeswift/runtime@0.0.5

27 Apr 02:20
Compare
Choose a tag to compare

Patch Changes

  • e14fac2: Opt in to useInsertionEffect with Style control.

  • a8272e8: Fix Width control mapping so that it uses maxWidth instead of width.

  • 6b36df9: Suppress React warning when passing ref to function component.

  • c410d49: Revert change that used react-is to detect when to forward ref.

    Unfortunately using react-is won't work since isForwardRef doesn't give the correct result is the component uses React.memo, React.lazy, or similar variants. Also, react-is would need to be a peer dependency, increasing the integration burden.

@makeswift/runtime@0.0.4

26 Apr 15:31
Compare
Choose a tag to compare

Patch Changes

  • 82f6afc: Suppress findDOMNode warning.

  • a1c8c6a: Fix issue with Navigation builtin component and using colors.

  • 5756f33: Use react-is to determine when to forward ref.

  • a87afe0: Automatically find DOM nodes if registered component doesn't forward the ref.

    This functionality relies on findDOMNode, which has been deprecated in StrictMode. This means that in StrictMode users will see a warning. Moreover, since we're passing the ref prop to registered components regardless, if the ref isn't forwarded, users will see a warning from React during development prompting them to forward the ref.