다형성 연관 두 가입 양식과 하나의 로그인 양식

Question

저는 현재 직업 게시판 웹 응용 프로그램을 구축하고 있습니다. 두 가지 유형의 사용자와 고용주가 있습니다. 나는 그것이 양식을 가입의에 대한 사용자의 두 가지 유형이 Hired - Job Search Marketplace. Job Hunting Simplified!가 무엇을하고 있는지 예를 들어, 다른 가입 페이지 있지만 하나의 로그인 페이지를 갖고 싶어, 여기에 내가 지금까지

Routes.rb

Rails.application.routes.draw do 
    root 'home#index' 

    resources :profiles, except: [:new, :create] 
    resources :companies, except: [:new, :create] 
    devise_for :users, skip: [:registrations, :sessions] 
    devise_scope :user do 
    get '/login' => 'devise/sessions#new', as: 'new_user_session' 
    post '/login' => 'devise/sessions#create', as: 'user_session' 
    match 'logout', to: 'devise/sessions#destroy', as: :destroy_user_session, via: Devise.mappings[:user].sign_out_via 
    end 
    get '/new_employer' => 'companies#new', as: 'new_employer' 
    post '/new_employer' => 'companies#create' 
    get '/new_applicant' => 'profiles#new', as: 'new_applicant' 
    post '/new_applicant' => 'profiles#create' 
end 

를 한 일이다

User.rb

class User < ApplicationRecord 
    # Include default devise modules. Others available are: 
    # :confirmable, :lockable, :timeoutable and :omniauthable 
    devise :database_authenticatable, :registerable, 
     :recoverable, :rememberable, :trackable, :validatable 
    belongs_to :user_profile, polymorphic: true 
    scope :employer?, -> { where(user_profile_type: 'Company') } 
    scope :applicant?, -> { where(user_profile_type: 'Profile') } 
    scope :admin?, -> { where(admin: true) } 
end 

Companies_controller.rb

class CompaniesController < ApplicationController 
    before_action :set_company, only: [:show, :edit, :update, :destroy] 
    # GET /companies 
    # GET /companies.json 
    def index 
    @companies = Company.all 
    end 

    # GET /companies/1 
    # GET /companies/1.json 
    def show 
    end 

    # GET /companies/new 
    def new 
    @company = Company.new 
    @company.build_user 
    end 

    # GET /companies/1/edit 
    def edit 
    end 

    # POST /companies 
    # POST /companies.json 
    def create 
    @company = Company.new(company_params) 

    respond_to do |format| 
     if @company.save 
     format.html { redirect_to @company, notice: 'Company was successfully created.' } 
     format.json { render :show, status: :created, location: @company } 
     else 
     format.html { render :new } 
     format.json { render json: @company.errors, status: :unprocessable_entity } 
     end 
    end 
    end 

    # PATCH/PUT /companies/1 
    # PATCH/PUT /companies/1.json 
    def update 
    respond_to do |format| 
     if @company.update(company_params) 
     format.html { redirect_to @company, notice: 'Company was successfully updated.' } 
     format.json { render :show, status: :ok, location: @company } 
     else 
     format.html { render :edit } 
     format.json { render json: @company.errors, status: :unprocessable_entity } 
     end 
    end 
    end 

    # DELETE /companies/1 
    # DELETE /companies/1.json 
    def destroy 
    @company.destroy 
    respond_to do |format| 
     format.html { redirect_to companies_url, notice: 'Company was successfully destroyed.' } 
     format.json { head :no_content } 
    end 
    end 

    private 
    # Use callbacks to share common setup or constraints between actions. 
    def set_company 
     @company = Company.find(params[:id]) 
    end 

    # Never trust parameters from the scary internet, only allow the white list through. 
    def company_params 
     # params.require(:company).permit(:company_name, :company_website) 
     params.require(:company).permit! 
    end 

end 

기업 /_form.html.erb

<%= simple_form_for(@company, url: new_employer_path) do |f| %> 
    <%= f.error_notification %> 

    <div class="form-inputs"> 
    <%= f.input :company_name %> 
    <%= f.input :company_website %> 
    </div> 

    <%= f.simple_fields_for :user do |u| %> 
     <div class="col-lg-6"> 
      <%= u.input :email %> 
     </div> 

     <div class="col-lg-6"> 
      <%= u.input :password %> 
     </div> 

     <div class="col-lg-6"> 
      <%= u.input :password_confirmation %> 
     </div> 
    <% end %> 


    <div class="form-actions"> 
    <%= f.button :submit %> 
    </div> 
<% end %> 

어떻게하면 되겠습니까? 고마워요.

Answer 1

나는 당신의 문제를 완전히 이해하고 있는지 잘 모르겠다.하지만 로그인 할 때 devise의 기본 로그인을 사용할 수 있기 때문에 두 개의 다른 sign_up 페이지가 필요할 것 같다.

나는 정의 RegistrationController를 작성하고 Devise::RegistrationsController

에서 상속 당신은 당신의 경로 같은 설정 뭔가 할 수 것입니다 :

devise_for :users, controllers: { registrations: 'registrations' } 

devise_scope :user do 
    post '/user/create_applicant', to: 'registrations#create_applicant' 
    post '/user/create_employer', to: 'registrations#create_employer' 
end 

을 그리고 당신은 만들 수 있습니다 귀하의 registrations_controller이

class RegistrationsController < Devise::RegistrationsController 
    def create_applicant 
    # write your logic here 
    end 


    def create_employer 
    # write your logic here 
    end 
end 

같은