v6.0.0

What's new?

This release adds support for more flexible pricing and privileged transitions. Privileged transitions are transaction process transitions that need to be run from a secure context, i.e. the backend. Privileged transitions are a new feature that your transaction process needs to take into use. However, you can opt-out by reversing changes in PR #1314.

This support for privileged transitions adds integration to the FTW API endpoints added in #1301 .

Transaction line items

The line items that define the pricing of a transaction are now defined securely in the backend. This means that privileged transitions can safely define the line items in the backend based on the booking data, and the pricing can be fully customized in FTW. This means changing commissions, adding extra line items for discounts, etc.

Important note

The EstimatedBreakdownMaybe component that is used in the ListingPage will no longer internally define the pricing line items. Instead, the /api/transaction-line-items endpoint will be used to fetch the line items.

This means that the same place that defines the line items for privileged transitions is also used for the price estimation. This also means that any pricing customizations will need to be migrated to the transactionLineItems function in server/api-util/lineItems.js that will become the main customization point for describing pricing when privileged transitions are the default.

Note 2: If you have just changed bookingUnitType from 'line-item/night' to 'line-item/day', you need to make that change also in this server setup: server/api-util/lineItems.js.

Using privileged transitions

If you want to change privileged transitions or opt-out of those, you can edit the isPrivileged function in src/util/transaction.js and add the transitions there. After that, those transitions will automatically go through the backend.

Note that we will provide more specific documentation for this when the privileged transitions become the default. Also note that using privileged transitions requires a process change with Flex CLI.

Customizing pricing

As mentioned earlier, the transactionLineItems function in server/api-util/lineItems.js will become the main customization point to describe the pricing in a transaction.

Development

The command yarn run dev now starts a server that serves the /api/* endpoints of the Node server. This way you can enjoy code hot reload while developing your pricing logic.

Changes

• [change] Use privileged transitions for price calculation by default and update the process alias. #1314
• [add] Add client secret enquiry to 'yarn run config' script #1313
• [change] Add UI support for flexible pricing and privileged transitions. Note that this requires updating the booking breakdown estimation code that is now done in the backend. #1310
• [add] Add local API endpoints for flexible pricing and privileged transitions #1301
• [fix] yarn run dev-backend was expecting NODE_ENV. #1303

v5.0.0

v5.0.0 Changes

• [change] Streamlining filter setup. Everyone who customizes FTW-templates needs to update filters
  and unfortunately, the related code has been spread out in multiple UI containers.

  Now, filters are more configurable through marketplace-custom-config.js. You can just add new
  filter configs to filters array in there - and that should be enough for creating new filters
  for extended data.

  If you are creating a totally new filter component, you can take it into use in a single file:
  src/containers/SearchPage/FilterComponent.js

  In addition, we have renamed couple of container components:

  • SearchFilters -> SearchFiltersPrimary
  • SearchFiltersPanel -> SearchFiltersSecondary (SearchFiltersMobile has kept its name.)

  SortBy filter's state is also tracked similarly as filters. From now on, the state is kept in
  MainPanel and not in those 3 different UI containers.

  Read more from the related PR, and Flex Docs
  #1296

v4.5.0

v4.5.0 Changes

• [fix] In some situations, ProfileMenu has began to overflow on TopbarDesktop.
  #1290
• [change] Update dependencies (patch updates only)
  #1291
• [change] Refactor server API routes into separate files.
  #1294
• [change] Start the backend API router in dev mode with a dev server.
  #1297

v4.4.3

v4.4.3 Changes

• [fix] Allow white space on Japanese bank account info. Japan collects bank name and account owner
  name in addition to routing numbers. #1287
• [fix] wrongly named default props handleSubmit renamed to onSubmit
  #1288

v4.4.2

v4.4.2 Changes

• [fix] Handle deleted reviews in ActivityFeed #1283

v4.4.1

v4.4.1 Changes

• [change] Improve the search page sorting and filters UI for different screen sizes #1280

v4.4.0

v4.4.0 Changes

• [add] Search result sorting #1277
• [change] Move category and amenities search filters from primary filters to secondary filters. #1275

v4.3.0

v4.3.0 Changes

• [change] Redirect user back to Stripe during Connect Onboarding Flow when user is returned to
  failure URL provided that the Account Link generation is successful.
  #1269
• [fix] Don't flash listing closed text on mobile view of BookingPanel when the listing data is
  not loaded yet. Instead, check that text is shown only for closed listings.
  #1268
• [change] Use some default values to improve Stripe Connect onboarding. When creating a new Stripe
  the account we will pass the account type, business URL and MCC to Stripe in order to avoid a
  couple of steps in Connect Onboarding. We will also pass tos_shown_and_accepted flag. This PR
  will bring back the previously used accountToken which is now used for passing e.g. the account
  type to Stripe. #1267
• [change] Update Modal component to have option to use Portal with usePortal flag. Keep also
  possibility to use modals without Portal because of ModalInMobile component.
  #1258

v4.2.0

v4.2.0 Changes

• [add] Show a banner when a user is logged in with limited access.
  #1259
  #1261
• [add] Support for logging in as a user from Console.
  #1254
• [change] Add handlebars 4.5.3 and serialize-javascript 2.1.1 to resolutions in package.json.
  #1251

v4.1.0

v4.1.0 Changes

• [fix] Remove unused 'invalid' prop that breaks some versions of Final Form
  #1255
• [fix] Fix console.warn functions. #1252
• [add] Add missing countries (e.g. MX and JP) to StripeBankAccountTokenInput validations.
  #1250