Skip to content

v5.4.0
Compare
Choose a tag to compare
@Gnito Gnito released this 20 Aug 09:23
· 260 commits to main since this release
v5.4.0
e5e3e2a
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

This release prepares the template to work with 2 new access control features:

  • The currentUser entity will have state attribute.
    • The possible values are 'pending-approval', 'active', and 'banned'.
    • The 'pending-approval' state is a completely new state.
      • This state is only used if marketplace operator has manually enabled the user approval process from Access control asset
    • Read more: #428
  • Private marketplace mode
    • Set through Access control page on Console
    • The asset /general/access-control.json is fetched o check marketplace.private: true/false flag
    • Read more: #434

Note: It might take some time before those features are fully released. I.e. this release just prepares Sharetribe Web Template for the upcoming change.

Translations

  "InquiryForm.userPendingApprovalError": "Oops, something went wrong. You don't have permission to make inquiries",
  "NoAccessPage.userPendingApproval.schemaTitle": "No user approval",
  "NoAccessPage.userPendingApproval.heading": "Your account is waiting for approval",
  "NoAccessPage.userPendingApproval.content": "Your account needs to be approved by the {marketplaceName} team before you can start using it.",

Changes v5.4.0

  • [change] auth.duck.js: login flow should wait for currentUser entity be loaded.
    #436

  • [add] Access control: private marketplace mode

    • Fetch a new asset: /general/access-control.json to check private: true/false flag
    • Make SearchPage, ListingPage, ProfilePage, Styleguide require authentication
    • Ensure currentUser entity is loaded before loadData on client-side
    • Restrict data load & add redirections for SearchPage, ListingPage, and ProfilePage

    #434

  • [add] Access control: 'pending-approval' state for users.

    • Users will get "state", which is exposed through currentUser's attribute
    • A new state is "pending-approval", which restricts user from initiating transactions and posting
      listings.
    • In addition, 'banned' users will also have state 'banned'.
    • Extra: Routes.js: do not allow banned users to auth pages
    • [fix]: InboxPage.duck.js: include deleted and banned attributes
    • [fix]: ModalMissingInformation: only 'active' users get this modal shown
    • [fix]: Inquiry modal: open the modal after authentication
    • Some util-file imports have been reordered (might cause conflicts)

    #428

  • [fix] SearchPage: SearchFiltersMobile (modal) should be above topbar.
    #432

Assets 2
Loading