Trello clone with Phoenix and React (第九章节)

这篇文章属于基于Phoenix Framework 和React的Trello系列

Adding board members

On the last part we created the boards table, the Board model and we also generated the controller which will be in charge of listing and creating new boards for the authenticated users. We also coded the front-end so the boards and the creation form could be displayed. Recalling where we left it, after receiving the successful response from the controller while creating a new board, we wanted to redirect the user to its view so he could see all the details and add more existing users as members. Let’s do this!

The React view component

Before continuing let’s take a look at the React routes:

  1. // web/static/js/routes/index.js
  3. import { IndexRoute, Route }        from 'react-router';
  4. import React                        from 'react';
  5. import MainLayout                   from '../layouts/main';
  6. import AuthenticatedContainer       from '../containers/authenticated';;
  7. import BoardsShowView               from '../views/boards/show';
  8. // ...
  10. export default (
  11.   <Route component={MainLayout}>
  12.     ...
  14.     <Route path="/" component={AuthenticatedContainer}>
  15.       <IndexRoute component={HomeIndexView} />
  17.       ...
  19.       <Route path="/boards/:id" component={BoardsShowView}/>
  20.     </Route>
  21.   </Route>
  22. );

The /boards/:id route is going to be handled by the BoardsShowView component that we need to create:

  1. // web/static/js/views/boards/show.js
  3. import React, {PropTypes}   from 'react';
  4. import { connect }          from 'react-redux';
  6. import Actions              from '../../actions/current_board';
  7. import Constants            from '../../constants';
  8. import { setDocumentTitle } from '../../utils';
  9. import BoardMembers           from '../../components/boards/members';
  12. class BoardsShowView extends React.Component {
  13.   componentDidMount() {
  14.     const { socket } = this.props;
  16.     if (!socket) {
  17.       return false;
  18.     }
  20.     this.props.dispatch(Actions.connectToChannel(socket, this.props.params.id));
  21.   }
  23.   componentWillUnmount() {
  24.     this.props.dispatch(Actions.leaveChannel(this.props.currentBoard.channel));
  25.   }
  27.   _renderMembers() {
  28.     const { connectedUsers, showUsersForm, channel, error } = this.props.currentBoard;
  29.     const { dispatch } = this.props;
  30.     const members = this.props.currentBoard.members;
  31.     const currentUserIsOwner = this.props.currentBoard.user.id === this.props.currentUser.id;
  33.     return (
  34.       <BoardMembers
  35.         dispatch={dispatch}
  36.         channel={channel}
  37.         currentUserIsOwner={currentUserIsOwner}
  38.         members={members}
  39.         connectedUsers={connectedUsers}
  40.         error={error}
  41.         show={showUsersForm} />
  42.     );
  43.   }
  46.   render() {
  47.     const { fetching, name } = this.props.currentBoard;
  49.     if (fetching) return (
  50.       <div className="view-container boards show">
  51.         <i className="fa fa-spinner fa-spin"/>
  52.       </div>
  53.     );
  55.     return (
  56.       <div className="view-container boards show">
  57.         <header className="view-header">
  58.           <h3>{name}</h3>
  59.           {::this._renderMembers()}
  60.         </header>
  61.         <div className="canvas-wrapper">
  62.           <div className="canvas">
  63.             <div className="lists-wrapper">
  64.               {::this._renderAddNewList()}
  65.             </div>
  66.           </div>
  67.         </div>
  68.       </div>
  69.     );
  70.   }
  71. }
  73. const mapStateToProps = (state) => ({
  74.   currentBoard: state.currentBoard,
  75.   socket: state.session.socket,
  76.   currentUser: state.session.currentUser,
  77. });
  79. export default connect(mapStateToProps)(BoardsShowView);

When it mounts it will connect to the board’s channel using the user socket we already created on part 7. When rendering it will first check if the fetching attribute is set to true, if so it will render a spinner while the board’s data is still being fetched. As we can see it takes its props from the currentBoard element in the state which is created by the following reducer.

The reducer and actions creator

As a starting point of the current board state we will only need to store the board data, the channel and the fetching flag:

  1. // web/static/js/reducers/current_board.js
  3. import Constants  from '../constants';
  5. const initialState = {
  6.   channel: null,
  7.   fetching: true,
  8. };
  10. export default function reducer(state = initialState, action = {}) {
  11.   switch (action.type) {
  12.     case Constants.CURRENT_BOARD_FETHING:
  13.       return { ...state, fetching: true };
  15.     case Constants.BOARDS_SET_CURRENT_BOARD:
  16.       return { ...state, fetching: false, ...action.board };
  18.     case Constants.CURRENT_BOARD_CONNECTED_TO_CHANNEL:
  19.       return { ...state, channel: action.channel };
  21.     default:
  22.       return state;
  23.   }
  24. }

Let’s take a look to the current_board actions creator to check how do we connect to the channel and dispatch all the necessary data:

  1. // web/static/js/actions/current_board.js
  3. import Constants  from '../constants';
  5. const Actions = {
  6.   connectToChannel: (socket, boardId) => {
  7.     return dispatch => {
  8.       const channel = socket.channel(`boards:${boardId}`);
  10.       dispatch({ type: Constants.CURRENT_BOARD_FETHING });
  12.       channel.join().receive('ok', (response) => {
  13.         dispatch({
  14.           type: Constants.BOARDS_SET_CURRENT_BOARD,
  15.           board: response.board,
  16.         });
  18.         dispatch({
  19.           type: Constants.CURRENT_BOARD_CONNECTED_TO_CHANNEL,
  20.           channel: channel,
  21.         });
  22.       });
  23.     };
  24.   },
  26.   // ...
  27. };
  29. export default Actions;

Just as with the UserChannel, we use the socket to create a new channel identified as boards:${boardId} and we join it, receiving as response the JSON representation of the board, which will be dispatched to the store along with the BOARDS_SET_CURRENT_BOARD action. From now on it will be connected to the channel receiving any change done to the board by any member, refreshing automatically those updates in the screen thanks to React and Redux. But first we need to create the BoardChannel.

The BoardChannel

Although almost all of the remaining functionality is going to be placed in this module, we are now going to just create a very simple version of it:

  1. # web/channels/board_channel.ex
  3. defmodule PhoenixTrello.BoardChannel do
  4.   use PhoenixTrello.Web, :channel
  5.   alias PhoenixTrello.Board
  7.   def join("boards:" <> board_id, _params, socket) do
  8.     board = get_current_board(socket, board_id)
  10.     {:ok, %{board: board}, assign(socket, :board, board)}
  11.   end
  13.   defp get_current_board(socket, board_id) do
  14.     socket.assigns.current_user
  15.     |> assoc(:boards)
  16.     |> Repo.get(board_id)
  17.   end
  18. end

The join method gets the current board from the assigned user in the socket, returns it and assigns it to the socket so its available for future messages.

第九章：增加董事会成员 - 图1

Board members

Once the board is displayed to the user, the following step is to allow him to add other existing users as members so they can work together on it. To associate boards with other users we have to create a new table to store this relation. Let’s jump to the console and run:

  1. $ mix phoenix.gen.model UserBoard user_boards user_id:references:users board_id:references:boards

We need to update a bit the resulting migration file:

  1. # priv/repo/migrations/20151230081546_create_user_board.exs
  3. defmodule PhoenixTrello.Repo.Migrations.CreateUserBoard do
  4.   use Ecto.Migration
  6.   def change do
  7.     create table(:user_boards) do
  8.       add :user_id, references(:users, on_delete: :delete_all), null: false
  9.       add :board_id, references(:boards, on_delete: :delete_all), null: false
  11.       timestamps
  12.     end
  14.     create index(:user_boards, [:user_id])
  15.     create index(:user_boards, [:board_id])
  16.     create unique_index(:user_boards, [:user_id, :board_id])
  17.   end
  18. end

Apart from the null constraints, we are going to add a unique index for the user_id and the board_id so a User can’t be added twice to the same Board. After running the necessary mix ecto.migrate lets head to the UserBoard model:

  1. # web/models/user_board.ex
  3. defmodule PhoenixTrello.UserBoard do
  4.   use PhoenixTrello.Web, :model
  6.   alias PhoenixTrello.{User, Board}
  8.   schema "user_boards" do
  9.     belongs_to :user, User
  10.     belongs_to :board, Board
  12.     timestamps
  13.   end
  15.   @required_fields ~w(user_id board_id)
  16.   @optional_fields ~w()
  18.   def changeset(model, params \\ :empty) do
  19.     model
  20.     |> cast(params, @required_fields, @optional_fields)
  21.     |> unique_constraint(:user_id, name: :user_boards_user_id_board_id_index)
  22.   end
  23. end

Nothing unusual about it, but we also need to add this new relationships to the User model:

  1. # web/models/user.ex
  3. defmodule PhoenixTrello.User do
  4.   use PhoenixTrello.Web, :model
  5.   # ...
  7.   schema "users" do
  8.     # ...
  10.     has_many :user_boards, UserBoard
  11.     has_many :boards, through: [:user_boards, :board]
  13.     # ...
  14.   end
  16.   # ...
  17. end

We have two more relationships, but the one that matters the most to us is the :boards one, which we are going to use for security checks. Let’s also add the collection to the Board model:

  1. # web/models/board.ex
  3. defmodule PhoenixTrello.Board do
  4.   # ...
  6.   schema "boards" do
  7.     # ...
  9.     has_many :user_boards, UserBoard
  10.     has_many :members, through: [:user_boards, :user]
  12.     timestamps
  13.   end
  14. end

By doing these changes now we can differentiate between boards created by a user and boards where the user has been invited to. This is very important because when a user is in the board’s view we only want to show the members form if he is the original creator. We also want to automatically add the creator as a member so he gets listed by default, therefore we have to make a small change in the BoardController:

  1. # web/controllers/api/v1/board_controller.ex
  3. defmodule PhoenixTrello.BoardController do
  4.   use PhoenixTrello.Web, :controller
  5.   #...
  7.   def create(conn, %{"board" => board_params}) do
  8.     current_user = Guardian.Plug.current_resource(conn)
  10.     changeset = current_user
  11.       |> build_assoc(:owned_boards)
  12.       |> Board.changeset(board_params)
  14.     if changeset.valid? do
  15.       board = Repo.insert!(changeset)
  17.       board
  18.       |> build_assoc(:user_boards)
  19.       |> UserBoard.changeset(%{user_id: current_user.id})
  20.       |> Repo.insert!
  22.       conn
  23.       |> put_status(:created)
  24.       |> render("show.json", board: board )
  25.     else
  26.       conn
  27.       |> put_status(:unprocessable_entity)
  28.       |> render("error.json", changeset: changeset)
  29.     end
  30.   end
  31. end

Note how we build the new UserBoard association and insert it after previously checking if the board is valid.

The board members component

This component will display all the board’s members avatars and the form to add new ones:

第九章：增加董事会成员 - 图2

As you can see, thanks to the previous change in the BoardController, the owner will be displayed as the only member for now. Let’s see how this component will look like:

  1. // web/static/js/components/boards/members.js
  3. import React, {PropTypes}       from 'react';
  4. import ReactGravatar            from 'react-gravatar';
  5. import classnames               from 'classnames';
  6. import PageClick                from 'react-page-click';
  7. import Actions                  from '../../actions/current_board';
  9. export default class BoardMembers extends React.Component {
  10.   _renderUsers() {
  11.     return this.props.members.map((member) => {
  12.       const index = this.props.connectedUsers.findIndex((cu) => {
  13.         return cu === member.id;
  14.       });
  16.       const classes = classnames({ connected: index != -1 });
  18.       return (
  19.         <li className={classes} key={member.id}>
  20.           <ReactGravatar className="react-gravatar" email={member.email} https/>
  21.         </li>
  22.       );
  23.     });
  24.   }
  26.   _renderAddNewUser() {
  27.     if (!this.props.currentUserIsOwner) return false;
  29.     return (
  30.       <li>
  31.         <a onClick={::this._handleAddNewClick} className="add-new" href="#"><i className="fa fa-plus"/></a>
  32.         {::this._renderForm()}
  33.       </li>
  34.     );
  35.   }
  37.   _renderForm() {
  38.     if (!this.props.show) return false;
  40.     return (
  41.       <PageClick onClick={::this._handleCancelClick}>
  42.         <ul className="drop-down active">
  43.           <li>
  44.             <form onSubmit={::this._handleSubmit}>
  45.               <h4>Add new members</h4>
  46.               {::this._renderError()}
  47.               <input ref="email" type="email" required={true} placeholder="Member email"/>
  48.               <button type="submit">Add member</button> or <a onClick={::this._handleCancelClick} href="#">cancel</a>
  49.             </form>
  50.           </li>
  51.         </ul>
  52.       </PageClick>
  53.     );
  54.   }
  56.   _renderError() {
  57.     const { error } = this.props;
  59.     if (!error) return false;
  61.     return (
  62.       <div className="error">
  63.         {error}
  64.       </div>
  65.     );
  66.   }
  68.   _handleAddNewClick(e) {
  69.     e.preventDefault();
  71.     this.props.dispatch(Actions.showMembersForm(true));
  72.   }
  74.   _handleCancelClick(e) {
  75.     e.preventDefault();
  77.     this.props.dispatch(Actions.showMembersForm(false));
  78.   }
  80.   _handleSubmit(e) {
  81.     e.preventDefault();
  83.     const { email } = this.refs;
  84.     const { dispatch, channel } = this.props;
  86.     dispatch(Actions.addNewMember(channel, email.value));
  87.   }
  89.   render() {
  90.     return (
  91.       <ul className="board-users">
  92.         {::this._renderUsers()}
  93.         {::this._renderAddNewUser()}
  94.       </ul>
  95.     );
  96.   }
  97. }

Basically it will loop through its members prop displaying their avatars. It will also display the add new button if the current user happens to be the owner of the board. When clicking this button the form will be shown, prompting the user to enter a member email and calling the addNewMember action creator when the form is submitted.

The addNewMember action creator

From now on, instead of using controllers to create and retrieve the necessary data for our React front-end we will move this responsibility into the BoardChannel so any change can be broadcasted to every joined user. Having this in mind let’s add the necessary action creators:

  1. // web/static/js/actions/current_board.js
  3. import Constants  from '../constants';
  5. const Actions = {
  6.   // ...
  8.   showMembersForm: (show) => {
  9.     return dispatch => {
  10.       dispatch({
  11.         type: Constants.CURRENT_BOARD_SHOW_MEMBERS_FORM,
  12.         show: show,
  13.       });
  14.     };
  15.   },
  17.   addNewMember: (channel, email) => {
  18.     return dispatch => {
  19.       channel.push('members:add', { email: email })
  20.       .receive('error', (data) => {
  21.         dispatch({
  22.           type: Constants.CURRENT_BOARD_ADD_MEMBER_ERROR,
  23.           error: data.error,
  24.         });
  25.       });
  26.     };
  27.   },
  29.   // ...
  31. }
  33. export default Actions;

The showMembersForm will make the form show or hide, easy as pie. The tricky part comes when we want to add the new member with the email provided by the user. Instead of making the typical http request we’ve been doing so far, we push the message members:add to the channel with the email as parameter. If we receiver an error we will dispatch it so it’s displayed in the screen. Why aren’t we handling the case for a success response? Because we are going to take a different approach, broadcasting the result to all the connected members.

The BoardChannel

Having this said let’s add the underlying message handler to the BoardChannel

``elixir

web/channels/board_channel.ex

defmodule PhoenixTrello.BoardChannel do

…

def handle_in(“members:add”, %{“email” => email}, socket) do try do board = socket.assigns.board user = User |> Repo.get_by(email: email)

  1.   changeset = user
  2.   |> build_assoc(:user_boards)
  3.   |> UserBoard.changeset(%{board_id: board.id})
  5.   case Repo.insert(changeset) do
  6.     {:ok, _board_user} ->
  7.       broadcast! socket, "member:added", %{user: user}
  9.       PhoenixTrello.Endpoint.broadcast_from! self(), "users:#{user.id}", "boards:add", %{board: board}
  11.       {:noreply, socket}
  12.     {:error, _changeset} ->
  13.       {:reply, {:error, %{error: "Error adding new member"}}, socket}
  14.   end
  15. catch
  16.   _, _-> {:reply, {:error, %{error: "User does not exist"}}, socket}
  17. end

end

…

end

  2. Phoenix channels handle incoming messages using the handle_in function and Elixir's powerful pattern matching to handle incoming messages. In our case the message name will be members:add, and it will be also be expecting an email parameter which will be matched to the corresponding variable. It will get the assigned board in the channel, find the user by his email and create a new UserBoard with both of them. If everything goes fine it will broadcast the message member:added to all the available connections passing the added user. Now let's take a closer look to this:
  4. PhoenixTrello.Endpoint.broadcast_from! self(), "users:#{user.id}", "boards:add", %{board: board}
  5. By doing this, it will be broadcasting the message boards:add along with the board to the UserChannel of the added member so the board suddenly appears in his invited boards list. This means we can broadcast any message to any channel from anywhere, which is awesome and brings a new bunch of possibilities and fun.
  7. To handle the member:added message in the front-end we have to add a new handler to the channel where it will dispatch the added member to the store:
  9. ```javascript
  10. // web/static/js/actions/current_board.js
  12. import Constants  from '../constants';
  14. const Actions = {
  15.   // ...
  17.   connectToChannel: (socket, boardId) => {
  18.     return dispatch => {
  19.       const channel = socket.channel(`boards:${boardId}`);
  21.       // ...
  23.       channel.on('member:added', (msg) => {
  24.         dispatch({
  25.           type: Constants.CURRENT_BOARD_MEMBER_ADDED,
  26.           user: msg.user,
  27.         });
  28.       });
  30.       // ...
  31.     }
  32.   },
  33. };
  35. export default Actions;

And we have to do exactly the same for the boards:add, but dispatching the board:

  1. // web/static/js/actions/sessions.js
  3. export function setCurrentUser(dispatch, user) {
  4.   channel.on('boards:add', (msg) => {
  5.     // ...
  7.     dispatch({
  8.       type: Constants.BOARDS_ADDED,
  9.       board: msg.board,
  10.     });
  11.   });
  12. };
  13. Finally, we need to update the reducers so both the new member and the new board are added into the application state:
  15. // web/static/js/reducers/current_board.js
  17. export default function reducer(state = initialState, action = {}) {
  18.   // ...
  20.   case Constants.CURRENT_BOARD_MEMBER_ADDED:
  21.     const { members } = state;
  22.     members.push(action.user);
  24.     return { ...state, members: members, showUsersForm: false };
  25.   }
  27.   // ...
  28. }
  29. // web/static/js/reducers/boards.js
  31. export default function reducer(state = initialState, action = {}) {
  32.   // ...
  34.   switch (action.type) {
  35.     case Constants.BOARDS_ADDED:
  36.       const { invitedBoards } = state;
  38.       return { ...state, invitedBoards: [action.board].concat(invitedBoards) };
  39.   }
  41.   // ...
  42. }

Now the new member’s avatar will appear in the list, and he will have access to the board and the necessary permissions to add and update new lists and cards.

第九章：增加董事会成员 - 图3

If we recall the BoardMembers component we previously described, the className of the avatar depends on wether the member id exists in the connectedUsers list prop or not. This list stores all the ids of the currently connected members to the board’s channel. To create and handle this list we will be using a longtime running stateful Elixir process, but we will do this on the next part. Meanwhile, don’t forget to check out the live demo and final source code:

Live demo Source code Happy coding!