faustjs

Major Changes

• c163fa5: BREAKING: Removed telemetry CLI commands for faust telemetry enable/disable/status for managing and viewing telemetry opt-in status. Telemetry functionality has been moved to the Faust WordPress plugin. Sites that previously opted in from CLI will no longer send telemetry data unless someone opts in from the WordPress side.

Patch Changes

• c163fa5: Adds block_editor_utils and experimental_app_router to telemetry events.

Minor Changes

• 8dcda28: Add support for RichText control fields.

  Add a source and selector in your block attributes string field:

  ...
  "attributes": {
  		"richText": {
  			"type": "string",
  			"source": "html",
  			"selector": ".rich-text",
  			"default": "Hello World"
  		}
  	}
  

  Then in your component definition make sure the selector specifier matches the component you want to render as rich text:

  <div
    style={styles}
    className="rich-text"
    dangerouslySetInnerHTML={{ __html: attributes.richText }}
  />
  

  Once the blocks are synced you will be able to use it as a RichText field.

Patch Changes

• 66c1e24: Publish Readme to NPM

Patch Changes

• c75ab2b: Bug: Quote blockset "output-path" to prevent issues with space in paths.

Patch Changes

• 78a061a: Fixed a bug that caused links to files in wp-content to be rewritten to the Faust Front-end site URL when they should not have been.
• 2559958: Bug Fix: Fixed missing call to autosave when using Post/Page previews.
• 75f5c80: Fixed a bug where links were rewritten to the Faust Front-end Site URL when using the post editor, resulting in those rewritten links being saved to the post content and guid fields when they shouldn't be. These links are now saved with the URL pointing to the WP site, as they should be. They are still rewritten at runtime to link to the Front-end Site URL when appropriate.

Patch Changes

• 626207b: Added: New util for fetching data on the client side. In a client component (use client), you can now use Apollo's useQuery to fetch data once your application is wrapped with the <FaustProvider> component. This new component is available via:

  import { FaustProvider } from '@faustwp/experimental-app-router/ssr';
  

Patch Changes

• 6276c80: Fix broken build from 0.2.0

Minor Changes

• 6e43598: BREAKING: Updated the following peer dependencies to new required minimums:

  • @apollo/experimental-nextjs-app-support: 0.4.1 -> 0.5.0
  • next: 12.1.6 -> 14.0.0
  • react: 17.0.2 -> 18.0.0
  • react-dom: 17.0.2 -> 18.0.0

• 6e43598: BREAKING: This package now requires Node 18+

Patch Changes

• b2c0fd3: Updated the settings page to improve descriptions and documentation links.

Minor Changes

• c29f83d: Add blockset command in @faust/cli and faustwp plugin.

  Add your blocks inside wp-blocks folder. Then run faust blockset to compile and upload the blocks into WordPress. Blocks will be available in the editor.

• d3d30aa: Added support for authenticated WPGraphQL introspection queries using FAUST_SECRET_KEY. It is no longer required to enable "Public Introspection" in WPGraphQL.

Patch Changes

• 3722ab3: Fix x-using header not appearing when i18n options are set in next.config.js

Minor Changes

• c29f83d: Add blockset command in @faust/cli and faustwp plugin.

  Add your blocks inside wp-blocks folder. Then run faust blockset to compile and upload the blocks into WordPress. Blocks will be available in the editor.

• d3d30aa: Added support for authenticated WPGraphQL introspection queries using FAUST_SECRET_KEY. It is no longer required to enable "Public Introspection" in WPGraphQL.

Patch Changes

• 03ee9e8: Bug Fix: Forces cli blockset command to use @wordpress/scripts package.

Patch Changes

• 604e9e3: Update block-editor-utils dependencies.

Patch Changes

• 9a84eb4: Allow CLI health checks to be skipped via --skip-health-checks argument

Minor Changes

• 77c5d4f: BREAKING: Removed cjs support. The experimental app router package now is ESM only.

Patch Changes

• 77c5d4f: Fixed an issue where the Apollo Client was being shipped to the browser client bundle resulting in large bundle sizes (150kb+). For more context: https://github.com/apollographql/apollo-client-nextjs/issues/95

Patch Changes

• ae69cfb: Feat: Add CheckboxControl field in block-editor-utils.
• ee8c08e: Feat: Add RangeControl field in block-editor-utils.

Patch Changes

• fcc6d37: Fixed a bug in the block editor screen where the preview link was missing the p and previewPathName query arguments after saving a draft.

Patch Changes

• b201ba2: Fixed a regression where an improper exit code was being thrown when 1. the NEXT_PUBLIC_WORDPRESS_URL environment variable was not set or 2. the GraphQL endpoint was not available

Patch Changes

• b2ad517: Added the onLogin server action to login a user:

  import { onLogin } from '@faustwp/experimental-app-router';
  
  <form action={loginAction}>
    <fieldset>
      <label htmlFor="usernameEmail">Username or Email</label>
      <input type="name" name="usernameEmail" />
    </fieldset>
  
    <fieldset>
      <label htmlFor="password">Password</label>
      <input type="password" name="password" />
    </fieldset>
  
    <button type="submit">Login</button>
  </form>;
  

• Updated dependencies [b201ba2]

  • @faustwp/[email protected]

Patch Changes

• 457933b: Feat: Handle NumberControl fields in the block-editor-utils.
• 40c836a: Feat: Handle RadioControl fields in the block-editor-utils.
• deb5767: Feat: Handle SelectControl fields in the block-editor-utils.
• db848c4: Feat: Handle TextControl fields in block-editor-utils.
• 1bb5e94: Feat: Handle ColorControl fields in block-editor-utils

Patch Changes

• a419252: Fixed an issue where persisted queries were not being enabled properly when setting the usePersistedQueries flag.

• cf887d3: Fixed bug where the "Edit Post" link was missing in the Faust Toolbar

• 795d956: Improved keyboard navigation within Toolbar menus, allowing for dropdowns to be toggled open with "enter"

  Note that the ToolbarItem component no longer uses the prop handleClick, instead relying on pass-through props in order to separate the click event from the the key event.

  <ToolbarItem onKeyDown={handleKeyDown} onClick={handleClick}>
    Log Out
  </ToolbarItem>