Class: Studio::OnboardingController

Inherits:
ApplicationController
  • Object
show all
Defined in:
app/controllers/studio/onboarding_controller.rb

Overview

The first-name onboarding step's two writes — capture a name, or record that the account skipped it. Ported from turf-monster (2026-08), where this ran as a local OnboardingController, because the same ask is wanted in every Studio app: McRitchie Studio, McRitchie Industries, and turf-monster all address people by name in email, and all three were going to write this controller.

What the ENGINE owns here is ONE STEP. What each HOST still owns is the SEQUENCE around it — turf walks welcome → first name → age → wallet; a hub app may ask nothing else. Hosts declare that through Studio.onboarding_steps_resolver, whose value this returns as next so the client keeps walking without a second round trip.

A plain host-inherited controller (same shape as StyleController and Studio::EmailsController): it renders no layout of its own, answers JSON only, and picks up the host's authentication from ApplicationController.

Routes are OPT-IN via Studio.draw_onboarding_routes — turf-monster owns these helper names until its adoption task deletes the local pair.

Constant Summary collapse

MAX_FIRST_NAME =

Both actions are for the freshly signed-in user, so authentication is the host's default require_authentication — no skip_before_action here.

40

Instance Method Summary collapse

Instance Method Details

#first_name ⇒ Object

POST /onboarding/first_name

Writes users.first_name, and backfills name when it is blank so the display-name chain has something better than an email prefix to show.



32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
 
# File 'app/controllers/studio/onboarding_controller.rb', line 32

def first_name
  value = params[:first_name].to_s.strip.gsub(/\s+/, " ").first(MAX_FIRST_NAME)

  if value.blank?
    return render json: { ok: false, error: "Enter your first name, or skip for now." },
                  status: :unprocessable_entity
  end

  rescue_and_log(target: current_user) do
    # update_columns, not update!: this runs seconds after signup, on an
    # account that may be mid-onboarding, and a validation failure elsewhere
    # on the record (a grandfathered reserved username, say) must not block a
    # first name. It also steps around any host before_save that DERIVES
    # first_name FROM name — turf's set_name_parts does exactly that, and
    # writing through it would discard the value we were just handed.
    attrs = { first_name: value }
    attrs[:name] = value if current_user.name.blank?
    current_user.update_columns(attrs)

    render json: { ok: true, first_name: value, next: remaining_steps }
  end
end

#skip_first_name ⇒ Object

POST /onboarding/skip_first_name

Session-scoped, deliberately: skipping means "not now", not "never". A later session can ask again (the field is still blank), which is the whole reason this is not a users column.



60
61
62
63
 
# File 'app/controllers/studio/onboarding_controller.rb', line 60

def skip_first_name
  session[Studio::FIRST_NAME_SKIP_SESSION_KEY] = true
  render json: { ok: true, next: remaining_steps }
end