Releases · sharetribe/web-template

15 Jan 14:14

Gnito

v7.0.0

ee7d32b

v7.0.0 Latest

Latest

This release updates Sharetribe Web Template to work with React v18 (v18.3.1)

Besides v18, there are also other improvements and fixes.

Notes for ppl taking update from this repo:

The changes have been made in the PR 523

react-dom has been split
react-dom/server is a separated from the rest of the package. Template loads this separately (but we kept the file structure the same). To get grasp of the changes to hydration flow, check especially these files:

src/index.js
src/app.js
server/index.js
server/dataLoader.js
server/renderer.js

sharetribe-scripts
The dependency had a somewhat embarrasing bug with Loadable Components setup causing hydration issue with v18. The earlier React versions were able to resolve the issue silently, but v18 is more strict to enforce that the server-side rendered (SSR) HTML matches with the HTML created on the first rendering pass on the browser / client-side rendering (CSR).

The fix was small (one-liner), but it caused UI issue on SearchPage (map layout was broken). Therefore, the new release for the sharetribe-scripts is going to be a major one (instead of a patch release).

Other hydration issues we encountered
There were some components that used typeof window === 'undefined' type of checks directly on rendering function. Those will cause hydration issues with React v18 (as SSR returns true and CSR returns false), if the check causes different HTML structure.

Similarly, some components used matchMedia to change HTML on for mobile and desktop layouts. With React v18, you need to make the first pass on CSR to match with the SSR. One way to do that is to track when the component is mounted:

const MyComponent = props => {
  const [mounted, setMounted] = useState(false);
  useEffect(() => {
    setMounted(true);
  }, []);
  
  const isMobileLayout =
    mounted && window?.matchMedia ? window.matchMedia(`(max-width: 767px)`)?.matches : true;

 return isMobileLayout ? <div>Hello</div> : <main>world</main>;
};

With this kind of code, the first CSR rendering does not pick 'desktop' layout. There will be a second rendering pass after the mounted flag is turned to true.

Dependency libraries
Several dependency libraries have been updated to support React v18.

Spreading key prop from list items throws a warning
Component's key can't be spread from collection of props anymore.

-        const { schemaType, ...fieldProps } = customFieldProps;
+        const { schemaType, key, ...fieldProps } = customFieldProps;
         return schemaType === SCHEMA_TYPE_MULTI_ENUM ? (
-          <SectionMultiEnumMaybe {...fieldProps} />
+          <SectionMultiEnumMaybe key={key} {...fieldProps} />

defaultProps and propTypes
React v18.3.1 has deprecated defaultProps in favor of JavaScripts (ES6) native default parameters for spread. This PR changes all the places, where defaultProps has been used. In addition, propTypes (on the same components) are also be removed on next React version (v19). Therefore, we have removed propTypes too and added the same information as JSDoc comment for the exported components.

If you want to postpone defaultProps removal, you could choose v18.2 instead of v18.3.1. The latter gives the warning about deprecation.

Most of the changes in this PR is about propTypes & JSDoc comments.
Note: there are still some components (~20) that needs propTypes to be removed, and we'll likely improve JSDocs while developing new features.

Tests
There was changes to the Testing Library setup (we started to use act as rendering became more asynchronous with the updated libraries). Note: act is imported differently between React v18.2 and v18.3.1. If you choose to use v18.2, you need to import act from the React Testing Library instead of importing it directly from React.

What about server components?
We didn't start to use server components at this point. It would affect only few public routes (landing page, search, listing and profile pages mainly) and we already have SSR in place for the public pages. Furthermore, relevant page schema for bots that don’t render JavaScript, won’t be available if loadData is not completed on the server.

You are of course, free to explore and try that approach yourself, but do notice that you'd need to start streaming the server content with renderToPipeableStream and React’s expectation is that the whole HTML is part of React app. Template renders only part of the DOM: the app UI is rendered to a string that is then injected inside public/index.html document.

Translation changes

New keys

  "EditListingAvailabilityPlanForm.delete": "Delete",

Note: this key was shared already before with Seats feature release (v6.3.0)

changed translations

  "CustomExtendedDataField.numberTooSmall": "The number must be greater than or equal to {min}",

Changes v7.0.0

This major release takes the React v17.0.2 into use.

[fix] EditListingWizard: fix a bug with YouTube field.
#533
[fix] CustomExtendedDataField.module.css: add missing customMediaQuery import.
#532
[change] This updates Sharetribe Web Template to use React v18 (v18.3.1). Some highlights:
- Several dependency libraries have been updated.
- Hydration is much more strict now. First render on client-side must match the server-side
  render.
#523
[add] Add currently available translations for DE.
#529
[fix] a link inside the inquiry message was invisible for the sender of the inquiry.
#528
[add] Add currently available translations for DE, ES, FR.
#527
[fix] AvailabilityPlanForm had a hard-coded "Delete" text.
#525
[add] Add currently available translations for DE, ES, FR.
#524
[change] Update the wording of the numberTooSmall error message for consistency.
#522

Assets 2

08 Jan 10:12

Gnito

v6.3.0

2f11379

v6.3.0

This release adds the support for handling multiple seats with default-booking transaction process.

NOTE 1:
the entire feature is not fully released
(as there should be a new config passed in from listing-types asset and change in Marketplace Console is not yet ready).

NOTE 2:
If you have modified email templates using CLI, you need to check that the booking breakdowns on sent emails work correctly with multiple seats. See #518

NOTE 3:
This release modifies the availability tab on EditListingWizard. The UI changes so that the weekly calendar will show only 1 list of available time ranges - and that list also includes exceptions. See the screenshots on #502

In addition to seats releated changes, this release contains a few smaller improvements and bug fixes. Check the full changes v6.3.0 list below.

Translations

New translation keys

  "BookingDatesForm.seatsPlaceholder": "Select...",
  "BookingDatesForm.seatsTitle": "Number of seats",
  "BookingTimeForm.seatsPlaceholder": "Select...",
  "BookingTimeForm.seatsTitle": "Number of seats",
  "EditListingAvailabilityPanel.WeeklyCalendar.exception": "Exception: {exception}",
  "EditListingAvailabilityPanel.WeeklyCalendar.seats": "{seats, plural, one {{seats} seat} other {{seats} seats}}",
  "EditListingAvailabilityPlanForm.selectTime": "Select time",
  "FieldSeatsInput.numberTooBig": "The number must be less than or equal to {max}",
  "FieldSeatsInput.numberTooSmall": "The number must be greater than or equal to {min}",
  "FieldSeatsInput.seatsError": "This field is required",
  "FieldSeatsInput.seatsLabel": "Seats",
  "FieldSeatsInput.seatsPlaceholder": "Seats",
  "FilterComponent.seatsLabel": "Seats",
  "InboxPage.seats": "Number of seats: {seats}",
  "NumberInput.decrementButton": "Decrement the value by one",
  "NumberInput.incrementButton": "Increment the value by one",
  "OrderBreakdown.baseUnitDaySeats": "{unitPrice} x {quantity, number} {quantity, plural, one {day} other {days}} x { seats, number } { seats, plural, one {seat} other {seats} }",
  "OrderBreakdown.baseUnitNightSeats": "{unitPrice} x {quantity, number} {quantity, plural, one {night} other {nights}} x { seats, number } { seats, plural, one {seat} other {seats} }",
  "OrderBreakdown.baseUnitHourSeats": "{unitPrice} x {quantity, number} {quantity, plural, one {hour} other {hours}} x { seats, number } { seats, plural, one {seat} other {seats} }",
  "SeatsFilter.labelSelected":"Seats: {seatCount}",

Note: FieldSeatsInput: min = 0, max is 9007199254740991 aka Number.MAX_SAFE_INTEGER

Deleted translation keys

  "EditListingAvailabilityPanel.WeeklyCalendar.exceptions": "Exceptions",

Changes v6.3.0

[fix] fix a bug with seats handling in email templates.
#518
[add] Add support for using multiple seats on default-booking process.
#502
[fix] ListingPageVariant: the #author anchor was not pointing to ListingPageVariant.
#515
[fix] target element didn't seem to work well with scroll-margin.
#513
[change] Require account type when creating a Stripe account
#512
[add] Add currently available translations for DE, ES, FR.
#511

Assets 2

26 Nov 12:05

SariSaar

v6.2.0

8852e72

v6.2.0

This release introduces updates to Stripe and Mapbox in the template.

Stripe

When collecting payout information from providers, the template no longer collects the user's bank account information. Instead, that information is collected in the Stripe Connect Onboarding flow.

In addition, the template supports setting a non-Stripe-supported currency for listings created with the default inquiry process.

Mapbox

The mapbox-gl-js library used in the template is updated v1.0.0 => v3.7.0. In addition, there is an update to the mapbox-sdk.js file that corresponds to the mapbox-sdk-js library and is included from a static folder for CSP purposes. See corresponding PR notes for details on license changes.

In addition, this release includes bug fixes and improvements.

Translation changes

New translation keys

  "CheckoutPage.incompatibleCurrency": "You're trying to initiate a payment using a currency not supported by Stripe. If you're using Stripe as your payment processor, you can only use currencies supported by Stripe.",
  "EditListingDetailsForm.incompatibleCurrency": "{marketplaceName} uses {marketplaceCurrency} as its currency. This listing type requires online payments, but Sharetribe's online payment system doesn't support {marketplaceCurrency} payments. If you want to publish a listing with this listing type, the currency of the marketplace needs to be changed.",
  "EditListingWizard.payoutModalInfoNew": "{marketplaceName} uses Stripe to process payments. Get verified with Stripe and add your payout details to receive money from transactions. Start by choosing your account type and country.",
  "StripeConnectAccountForm.accountTypes.company": "Company",
  "StripeConnectAccountForm.accountTypes.individual": "Individual",

Updated translation keys

  "EditListingWizard.payoutModalInfo": "{marketplaceName} uses Stripe to process payments. Get verified with Stripe and add your payout details to receive money from transactions.",
  "StripeConnectAccountForm.stripeToSText": "By moving forward in the process, you agree to the {stripeConnectedAccountTermsLink}.",
  "StripeConnectAccountStatusBox.verificationNeededText": "Stripe needs some more information from you to verify your account.",
  "StripeConnectAccountStatusBox.verificationNeededTitle": "Complete verification to receive payments",

Deleted translation keys

  "StripeBankAccountTokenInputField.accountNumber.inline": "account number",
  "StripeBankAccountTokenInputField.accountNumber.label": "Bank account number",
  "StripeBankAccountTokenInputField.accountNumber.placeholder": "Type in bank account number…",
  "StripeBankAccountTokenInputField.accountNumber.required": "Bank account number is required.",
  "StripeBankAccountTokenInputField.accountOwnerName.inline": "account owner name",
  "StripeBankAccountTokenInputField.accountOwnerName.label": "Bank account owner name",
  "StripeBankAccountTokenInputField.accountOwnerName.placeholder": "Jane Doe",
  "StripeBankAccountTokenInputField.accountOwnerName.required": "Bank account owner name is required.",
  "StripeBankAccountTokenInputField.andBeforeLastItemInAList": " and",
  "StripeBankAccountTokenInputField.bankCode.inline": "bank code",
  "StripeBankAccountTokenInputField.bankCode.label": "Bank code",
  "StripeBankAccountTokenInputField.bankCode.placeholder": "Type in bank code…",
  "StripeBankAccountTokenInputField.bankCode.required": "Bank code is required.",
  "StripeBankAccountTokenInputField.bankName.inline": "bank name",
  "StripeBankAccountTokenInputField.bankName.label": "Bank name",
  "StripeBankAccountTokenInputField.bankName.placeholder": "Type in bank name…",
  "StripeBankAccountTokenInputField.bankName.required": "Bank name is required.",
  "StripeBankAccountTokenInputField.branchCode.inline": "branch code",
  "StripeBankAccountTokenInputField.branchCode.label": "Branch code",
  "StripeBankAccountTokenInputField.branchCode.placeholder": "Type in branch code…",
  "StripeBankAccountTokenInputField.branchCode.required": "Branch code is required.",
  "StripeBankAccountTokenInputField.branchName.inline": "branch name",
  "StripeBankAccountTokenInputField.branchName.label": "Branch name",
  "StripeBankAccountTokenInputField.branchName.placeholder": "Type in branch name…",
  "StripeBankAccountTokenInputField.branchName.required": "Branch name is required.",
  "StripeBankAccountTokenInputField.bsb.inline": "BSB",
  "StripeBankAccountTokenInputField.bsb.label": "BSB",
  "StripeBankAccountTokenInputField.bsb.placeholder": "Type in BSB…",
  "StripeBankAccountTokenInputField.bsb.required": "BSB is required.",
  "StripeBankAccountTokenInputField.clabe.inline": "CLABE",
  "StripeBankAccountTokenInputField.clabe.label": "CLABE",
  "StripeBankAccountTokenInputField.clabe.placeholder": "Type in CLABE…",
  "StripeBankAccountTokenInputField.clabe.required": "CLABE is required.",
  "StripeBankAccountTokenInputField.clearingCode.inline": "clearing code",
  "StripeBankAccountTokenInputField.clearingCode.label": "Clearing code",
  "StripeBankAccountTokenInputField.clearingCode.placeholder": "Type in clearing code…",
  "StripeBankAccountTokenInputField.clearingCode.required": "Clearing code is required.",
  "StripeBankAccountTokenInputField.genericStripeError": "Couldn't connect account number. Please double-check that your {inputs} are valid in {country}",
  "StripeBankAccountTokenInputField.genericStripeErrorIban": "Couldn't connect account number. Please double-check that your account number is valid in {country}",
  "StripeBankAccountTokenInputField.iban.inline": "IBAN",
  "StripeBankAccountTokenInputField.iban.label": "Bank account number (IBAN)",
  "StripeBankAccountTokenInputField.iban.placeholder": "DE89 3704 0044 0532 0130 00",
  "StripeBankAccountTokenInputField.iban.required": "Bank account number (IBAN) is required.",
  "StripeBankAccountTokenInputField.institutionNumber.inline": "institution number",
  "StripeBankAccountTokenInputField.institutionNumber.label": "Institution number",
  "StripeBankAccountTokenInputField.institutionNumber.placeholder": "Type in institution number…",
  "StripeBankAccountTokenInputField.institutionNumber.required": "Institution number is required.",
  "StripeBankAccountTokenInputField.routingNumber.inline": "routing number",
  "StripeBankAccountTokenInputField.routingNumber.label": "Routing number",
  "StripeBankAccountTokenInputField.routingNumber.placeholder": "Type in routing number…",
  "StripeBankAccountTokenInputField.routingNumber.required": "Routing number is required.",
  "StripeBankAccountTokenInputField.sortCode.inline": "sort code",
  "StripeBankAccountTokenInputField.sortCode.label": "Sort code",
  "StripeBankAccountTokenInputField.sortCode.placeholder": "Type in sort code…",
  "StripeBankAccountTokenInputField.sortCode.required": "Sort code is required.",
  "StripeBankAccountTokenInputField.transitNumber.inline": "transit number",
  "StripeBankAccountTokenInputField.transitNumber.label": "Transit number",
  "StripeBankAccountTokenInputField.transitNumber.placeholder": "Type in transit number…",
  "StripeBankAccountTokenInputField.transitNumber.required": "Transit number is required.",
  "StripeBankAccountTokenInputField.unsupportedCountry": "Country not supported: {country}",

Changes

[add] Remove bank account collection from the template, so that it is collected in the
Stripe Onboarding flow instead.
#470
[add] Add currently available translations for DE, ES, FR.
#508
[add] Add support for currencies not supported by Stripe in inquiry processes.
#493
SingeDatePicker: don't update value to dateData if it has the same timestamp has not changed.
#507
[change] Node v23.2 is failing. This adds engine rule for node (">=18.20.1 <23.2.0") for now.
#505
[change] Update mapbox-gl-js (v1.0.0 => v3.7.0) and mapbox-sdk-js (0.6.0 => 0.16.1) Note: Mapbox
license changed in v2 (and pricing for non-mapbox related map tiles)
https://github.com/mapbox/mapbox-gl-js/releases/tag/v2.0.0
#488
[change] Update default email template copy texts
#501
[fix] ConfirmSignupForm: show spinner. (Handling for confirmInProgress state was missing.)
#504
[fix] Topbar: if multiple custom links has the same text, the virtual DOM is confused.
#503
[fix] PaymentMethodsPage: full page load did not fetch defaultPaymentMethod.
#500
[change] Relax the Referrer-Policy to "origin".
#498
[fix] Open discard modal on ManageListingsPage only if scrolling is disabled. Fixes an issue where
opening the discard draft modal on mobile scrolled the page to the very bottom.
#497

Assets 2

06 Nov 14:56

SariSaar

v6.1.0

23c9017

v6.1.0

This release updates the Sharetribe Web Template to allow discarding draft listings on the ManageListingsPage. Read more about this feature in #474.

In addition, the release includes small bug fixes and refactorings.

Translation changes

New translation keys

  "DiscardDraftModal.close": "Close",
  "DiscardDraftModal.message": "This can't be undone.",
  "DiscardDraftModal.submit": "Discard draft",
  "DiscardDraftModal.title": "Are you sure you want to discard this draft?",
  "ManageListingCard.discardDraftLinkText": "Discard draft",
  "ManageListingCard.discardDraftText": "{discardDraftLink}",

Updated translations

-  "ManageListingCard.closeListingText": "close listing",
-  "ManageListingCard.closeListingTextOr": "or {closeListingLink}",
+  "ManageListingCard.closeListingText": "Close listing",
+  "ManageListingCard.closeListingTextOr": "{closeListingLink}",

Changes v6.1.0

[add] Add currently available translations for DE, ES, FR.
#495
[add] Add support for discarding draft listings on ManageListingsPage
#474
[fix] ManageListingCard: Menu has a regression bug on mobile layout. Note: if Menu component needs
to use full screenwidth on mobile, add preferScreenWidthOnMobile.
#494
[change] Refactor SingleDatePicker and DateRangePicker by combining date and its formatting. It
updates dateData if passed-in input value changes.
#492

Assets 2

01 Nov 08:47

Gnito

v6.0.1

1295283

v6.0.1

This fixes a bug on GA4 integration.

Changes v6.0.1

[fix] GA4 integration was faulty.
#489
[fix] FieldDateTimeInput.module.css: fix typo.
#487
[change] Update default email templates to use ICU's j pattern for datetimes.
#478
[change] Update default email templates to get link and button colors from asset.
#478

Assets 2

29 Oct 14:51

Gnito

v6.0.0

d3c7d77

v6.0.0

This major release takes React v17.0.2 into use.

The biggest change is the adoption of a new DatePicker and the removal of the outdated datepicker library, React Dates. This update was necessary, as React Dates still relies on deprecated React lifecycle functions, specifically componentWillReceiveProps and componentWillUpdate.

Another notable change with React v17 is that the callback functions of the useEffect hook are now asynchronous. You should review other v17 changes in the v17 changelog to verify if any of your customizations are affected.

The final highlight is that we have begun using a nonce for script-src in the Content Security Policy.

Notes from React v17 upate:

There has been changes to event delegation on React component tree.
- This change didn't seem to have practical consequences on this repository.
The callback functions of useEffect hook has become asynchronous!
- This had some consequences on this repository:
  - Topbar / CustomLinksMenu needed to be changed a bit
  - LayoutWrapperAccountSettingsSideNav aka account settings related pages needed to be changed a bit
    - In practice, these were automatic horizontal scroll-into-view tabs on mobile layout.
- If you have used useEffect hook with callback function on your customized client app, you should check that the callback does not rely on DOM objects.
  - If you need to have access to DOM for clean up process, you should use useLayoutEffect instead.

New DatePicker

This update removes the React Dates library from the codebase. It’s an outdated library that uses deprecated React lifecycle functions: componentWillReceiveProps and componentWillUpdate.

In place of a datepicker based on React Dates, this update includes a custom DatePicker component. The custom picker should look almost identical to the previous one, but there are a couple of changes:

Weekdays follow the "short" weekday syntax (provided by the Intl Web API).
It’s now possible to select a date range in both directions from the initially clicked boundary.
- Previously: If you clicked on Nov 15th, you could only select dates following that day (or the current date with the 'day' unit).
- With the new picker: If you click on Nov 15th, you can also select previous days. In this case, Nov 15th becomes the end date for the date range.

There are two different input mechanisms:

Primary method: Pointer (click input to open the date picker and choose calendar dates).
Secondary method: Keyboard
- Supported keys: Tab, Arrow keys, Enter, Esc, PageUp, PageDown, Home, End
- Note: If a pointer is hovering over the calendar, the secondary method won’t highlight the range, as the pointer is considered the primary date selection method.

This datepicker change affects several parts of the code:

When a user filters by date range on the search page.
When they book a listing on the listing page.
When they pick a week on the availability calendar on EditListingPage.
When they add availability exceptions to the default schedule.

Additionally, this PR modifies timeSlot handling. Returned timeSlots are now processed so that if there are two consecutive timeSlots (where one ends with the same timestamp as the next begins) and they have the same seat count, those timeSlots are merged into a single timeSlot.

Background:
The booking calendar fetches timeSlots for each month. For day- and night-based availability, this has worked fine, as we only check if a day has availability or not. However, there has been an issue with hour-based listings: we haven't had a good setup for multi-day bookings with hour-based listings. This is because timeslots.query returns availability between specified start and end times—meaning that separate fetches for each month create artificial borders, which disrupts continuous availability/timeSlot.

This change makes it easier for customizers to add bookings that take advantage of differently priced time units, allowing bookings that span a longer time window.

For example:
Bicycle rental has day price of $100 & hour price $5.
Customer rents it between 3:00 pm on Nov 15, 2024 and 10:00 am on Nov 18, 2024.
Custom price calculation could work like this:

Full days: 3 * $100 per day => $300

Extra hours: 19 * $5 per hour => $95

Total: $395

Note: this scenario assumes that hour-based availability is used with the listing type. The 'day' and 'night' time units reserve the given day (00:00 - 24:00) on the listing's time zone. So, they operate with a bit different availability concept.

Nonce

We removed unsafeInline & data from the script-src directive in the Content Security Policy.
- Instead, a nonce has been added for the affected cases:
  - The preloaded state passed from SSR
  - The code-splitted code-chunks.
  - Postponed work / todo: do something similar for the styles
- Note: This change might have implications when updating from the upstream (i.e., from this repo).
  - If you’ve added integrations (such as Google Tag Manager) that rely on <script> elements, you may need to adjust your custom code.

Translation changes

New translations

  "DatePicker.clearButton": "Clear value",
  "DatePicker.screenreader.blockedDate": "{date} is not available",
  "DatePicker.screenreader.chooseDate": "Choose {date}",
  "DatePicker.screenreader.chooseEndDate": "Choose {date} as the end date",
  "DatePicker.screenreader.chooseStartDate": "Choose {date} as the start date",
  "DatePicker.screenreader.nextMonthButton": "Next month",
  "DatePicker.screenreader.previousMonthButton": "Previous month",
  "DatePicker.screenreader.selectedDate": "{date} is selected",
  "DatePicker.screenreader.selectedEndDate": "{date} is selected as the end date",
  "DatePicker.screenreader.selectedStartDate": "{date} is selected as the start date",
  "DatePicker.todayButton": "Show today",

Updated translations

-   "NoAccessPage.postListings.schemaTitle": "No publishing rights",
-   "NoAccessPage.postListings.heading": "You don't have publishing rights",
-   "NoAccessPage.postListings.content": "To publish listings, you need to receive publishing rights from the {marketplaceName} team.",
+   "NoAccessPage.postListings.schemaTitle": "No posting rights",
+   "NoAccessPage.postListings.heading": "You don't have posting rights",
+   "NoAccessPage.postListings.content": "To post listings, you need to receive posting rights from the {marketplaceName} team.",

What about React v18?

We are planning to continue the update work to make the codebase compatible with React v18. However, we first want to test how the app performs with React v17. In practice, this means that the project leading to v18 will be on hold for about a month.

What we know about v18 so far:

MyComponent.defaultProps is deprecated, and its usage generates numerous warnings.
Hydration issues:
- Code-splitting needs to be reviewed on the sharetribe-scripts side.
- matchMedia usage needs refactoring to ensure that the first client-side rendering matches the server-side rendering (SSR).
- Topbar, SearchMap, and some other components require refactoring to ensure the first client-side rendering matches the SSR.
ReactDOM has been split into react-dom/server and react-dom/client
- This change may affect how SSR setup should be arranged.

[Changes] v6.0.0

This major release takes the React v17.0.2 into use.

The biggest change is taking a new DatePicker into use and removing the outdated datepicker library:
React Dates. The change was necessary as the React Dates still uses deprecated React life cycle
functions componentWillReceiveProps & componentWillUpdate.

Another notable change with the React v17 was with the callback functions of useEffect hook, which
became asynchronous. You should to check other v17 changes from v17 changelog to verify if your
customizations are affected somehow.

The last highlight is that we started to use nonce for script-src on Content Security Policy.

[change] This updates Sharetribe Web Template to use React v17.0.2.

Some highlights:
- The callback functions of useEffect hook has become asynchronous!
- There has been changes to event delegation on React component tree.
  - https://legacy.reactjs.org/blog/2020/10/20/react-v17.html#changes-to-event-delegation
  - This change didn't seem to have practical consequences on this repository.
#477
[add] CSP: start using nonce with script-src. This also removes data from script-src.
#485
[add] Remove React Dates datepicker library and add a new built-in DatePicker.

There are 3 new datepicker fields to be used with React Final Forms:
- FieldDateRangePicker
- FieldSingleDatePicker
- FieldDateRangeController
This swap is done because componentWillReceiveProps & componentWillUpdate functions, which are
used by the outdated React Dates library, are deprecated and removed from future React versions.

[#453]...

Assets 2

22 Oct 12:35

Gnito

v5.8.0

46e1e21

v5.8.0

This release updates the Sharetribe Web Template to accommodate upcoming improvements, including:

Pages:
- Aligning Block content to the left, center, or right side of the Block component.
- Block images can be wrapped with a link.
Listing & User fields:
- Providers can add a YouTube video URL, which will be displayed as a new section on the ListingPage.
- Users can add a YouTube video URL, which will be displayed as a new section on the ProfilePage.

Translations

New translations

  "CustomExtendedDataField.placeholderYoutubeVideoURL": "The URL of a YouTube video",
  "CustomExtendedDataField.notValidYoutubeVideoURL": "The URL you entered is not a valid YouTube URL.",

Changes v5.8.0

[add] Add currently available translations for DE, ES, FR.
#475
[add] Block images can be wrapped in a link if a link is configured via assets.
#464
[add] Add support for aligning content blocks based on asset
#469
[add] Update moment-timezone library to v0.5.46.
#472
[add] Update caniuselite, which is used by browserlist.
#471
[add] Add support for the youtubeVideoUrl schema type: listingPage and profilePage can now display
an embedded Youtube video #467
[add] Add currently available translations for DE, ES, FR.
#466

Assets 2

08 Oct 11:51

SariSaar

v5.7.0

00045a5

v5.7.0

This release introduces a capability to the template to handle viewing rights on a private marketplace.

Translations changes

New translation keys

  "NoAccessPage.viewListings.schemaTitle": "No viewing rights",
  "NoAccessPage.viewListings.heading": "You don't have viewing rights",
  "NoAccessPage.viewListings.content": "To view this content, you need to receive viewing rights from the {marketplaceName} team.",

Changes 2024-10-08

[add] Access control: Viewing rights.

When a user's viewing rights have been revoked:
- SearchPage redirects to NoAccessPage
- ListingPage redirects to NoAccessPage unless the user is viewing their own listing. Reviews are
  not displayed.
- ProfilePage redirects to NoAccessPage unless the user is viewing their own profile. Reviews are
  not displayed.
- TransactionPage does not show the OrderPanel for transactions at the inquiry state of booking or
  purchase processes.
#459

Assets 2

07 Oct 10:36

shareoc

v5.6.1

d54f8cc

v5.6.1

This release changes the logic of how a Call To Action button is rendered, as a change was made on how the permission assets are structured. Instead of using the enabled attribute, the CTA is enabled using the type attribute.

Note: The Call To Action button is not yet enabled in Console.

Changes 2024-10-07

[fix] Updated JSON asset schema structure from Console: Removed the enabled field, now using only
the type attribute for CTA status. #463
[add] Add currently available translations for DE, ES, FR.
#461

Assets 2

01 Oct 13:08

shareoc

v5.6.0

e310a56

v5.6.0

This release introduces support for restricting user transaction rights and adding a Call To Action link on the NoAccessPage component.

Note that a change to how the Call To Action link functions has been introduced in the newest release v5.6.1.

Translations changes

New translation keys

"InquiryForm.noTransactionRightsError": "Oops, something went wrong. You don't have transaction rights. <NoAccessLink>Read more about transaction rights.</NoAccessLink>",
"NoAccessPage.initiateTransactions.schemaTitle": "No transaction rights",
"NoAccessPage.initiateTransactions.heading": "You don't have transaction rights",
"NoAccessPage.initiateTransactions.content": "To start a transaction, you need to receive transaction rights from the {marketplaceName} team.",

Changed translations

- "InquiryForm.userPendingApprovalError": "Oops, something went wrong. You don't have permission to make inquiries",
- "NoAccessPage.postListings.heading": "You can't publish listings",
- "NoAccessPage.postListings.content": "You need to receive publishing rights from the {marketplaceName} team.",
+ "InquiryForm.userPendingApprovalError": "Oops, something went wrong. Your account is waiting for approval.",
+ "NoAccessPage.postListings.heading": "You don't have publishing rights",
+ "NoAccessPage.postListings.content": "To publish listings, you need to receive publishing rights from the {marketplaceName} team.",

Changes 2024-10-01

[add] Add support for CTAs on NoAccessPage
#455
[add] Add currently available translations for DE, ES, FR.
#458
[fix] Topbar: malformed custom link causes a 500 error on server.
#457
[fix] ListingPage.shared.js: import for convertMoneyToNumber was not made for priceForSchemaMaybe
function. #456
[add] Access control: Transaction rights
- When a user does not have the "initiateTransactions" permission in their
  effectivePermissionSet relationship and they try to initiate an order or send an inquiry, they
  are redirected to the NoAccessPage.
#450
[fix] InquiryForm: test code was committed earlier.
#452
[fix] EmailVerification: enforce that currentUser is fetched after verification.
#451
[fix] ListingPage: fix 0 as value of listing fields.
#449
[fix] EditListingDetailsPanel: fix 0 as value of listing fields.
#448
[fix] Currencies that the Stripe does not support should not cause 500 errors.
#447

Assets 2

Releases: sharetribe/web-template

v7.0.0

Notes for ppl taking update from this repo:

Translation changes

New keys

changed translations

Changes v7.0.0

v6.3.0

Translations

New translation keys

Deleted translation keys

Changes v6.3.0

v6.2.0

Stripe

Mapbox

Translation changes

New translation keys

Updated translation keys

Deleted translation keys

Changes

v6.1.0

Translation changes

New translation keys

Updated translations

Changes v6.1.0

v6.0.1

Changes v6.0.1

v6.0.0

Notes from React v17 upate:

New DatePicker

Nonce

Translation changes

New translations

Updated translations

What about React v18?

What we know about v18 so far:

[Changes] v6.0.0

v5.8.0

Translations

New translations

Changes v5.8.0

v5.7.0

Translations changes

New translation keys

Changes 2024-10-08

v5.6.1

Changes 2024-10-07

v5.6.0

Translations changes

New translation keys

Changed translations

Changes 2024-10-01