Why not call it commerce_referral?

Created on 25 January 2024, 10 months ago
Updated 29 January 2024, 10 months ago

Problem/Motivation

When I think recruiting I think job recruiting. The name suggests commerce support for a recruiting function.

But it is in fact commerce_referral like user_referal or uber_referral.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

✨ Feature request
Status

Closed: won't fix

Version

8.2

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States SocialNicheGuru

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @SocialNicheGuru
  • Status changed to Closed: won't fix 10 months ago
  • πŸ‡©πŸ‡ͺGermany ktpm

    Hi,

    thank you for your suggestion. I understand where this comes from.
    The name recruiting comes from the core entity, the recruitment, which everything in the module revolves around. We wanted to apply the same pattern as e.g. commerce_shipping, where the core entity is called "Shipment", but the module is called "shipping". We also thought of the module in terms of "getting a new customer on board of your shop", so "recruitment" seemed pretty accurate to us.
    Of course referral could have been fitting as well, but since this module is already up for over 3 years, we will want to leave the name as it is. Thank you for your understanding.

Production build 0.71.5 2024