<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.expertiza.ncsu.edu/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Spoudwa</id>
	<title>Expertiza_Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.expertiza.ncsu.edu/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Spoudwa"/>
	<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Special:Contributions/Spoudwa"/>
	<updated>2026-06-05T21:28:54Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.41.0</generator>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=Student_Task_View&amp;diff=125158</id>
		<title>Student Task View</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Student_Task_View&amp;diff=125158"/>
		<updated>2019-09-26T06:45:05Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: /* Redux */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Introduction ==&lt;br /&gt;
&lt;br /&gt;
This is the page you land on after you click on any of the tasks listed in the StudentTaskList view. Essentially, this is a page that helps you manage a particular task. It has a timeline with all the deadlines, links to pages for submissions, managing your team for that task, etc. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Rails ==&lt;br /&gt;
&lt;br /&gt;
The controller responsible for serving requests for this particular component can be found here https://github.com/ashwinrisbood/expertiza/blob/master/app/controllers/api/v1/student_task_controller.rb&lt;br /&gt;
The request is handled by the view action found in the code above. This action should return a json to the front-end with all the task related information of the the participant. The json that is rendered by this particular action is as below,&lt;br /&gt;
&lt;br /&gt;
[[File:ViewJson.PNG]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Redux ==&lt;br /&gt;
&lt;br /&gt;
The redux action making HTTP axios request to the Rails action specified above can be found under https://github.com/ashwinrisbood/expertiza/blob/master/client/src/redux/actions/StudentTaskView.js. This action makes a POST request as id as the parameter. The data received from the API is then passed on to the reducers to make changes to the state. The action is as follows,&lt;br /&gt;
&lt;br /&gt;
[[File:OnLoadAction.PNG]]&lt;br /&gt;
&lt;br /&gt;
There are multiple actions that are dispatched that make changes to different attributes of the state. The reducer code for this component can be found here https://github.com/ashwinrisbood/expertiza/blob/master/client/src/redux/reducers/StudentTaskView.js.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== React ==&lt;br /&gt;
&lt;br /&gt;
All React components can be found here https://github.com/ashwinrisbood/expertiza/blob/master/client/src/redux/reducers/StudentTaskView.js. The onLoad redux action is mapped to the component's props and is dispatched whenever the component mounts.&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=Student_Task_View&amp;diff=125157</id>
		<title>Student Task View</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Student_Task_View&amp;diff=125157"/>
		<updated>2019-09-26T06:26:52Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: /* Redux */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Introduction ==&lt;br /&gt;
&lt;br /&gt;
This is the page you land on after you click on any of the tasks listed in the StudentTaskList view. Essentially, this is a page that helps you manage a particular task. It has a timeline with all the deadlines, links to pages for submissions, managing your team for that task, etc. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Rails ==&lt;br /&gt;
&lt;br /&gt;
The controller responsible for serving requests for this particular component can be found here https://github.com/ashwinrisbood/expertiza/blob/master/app/controllers/api/v1/student_task_controller.rb&lt;br /&gt;
The request is handled by the view action found in the code above. This action should return a json to the front-end with all the task related information of the the participant. The json that is rendered by this particular action is as below,&lt;br /&gt;
&lt;br /&gt;
[[File:ViewJson.PNG]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Redux ==&lt;br /&gt;
&lt;br /&gt;
The redux action making HTTP axios request to the Rails action specified above can be found under https://github.com/ashwinrisbood/expertiza/blob/master/client/src/redux/actions/StudentTaskView.js. This action makes a POST request as id as the parameter. The data received from the API is then passed on to the reducers to make changes to the state. The action is as follows,&lt;br /&gt;
&lt;br /&gt;
[[File:OnLoadAction.PNG]]&lt;br /&gt;
&lt;br /&gt;
There are multiple actions that are dispatched that make changes to different attributes of the state. The reducer code for this component can be found here https://github.com/ashwinrisbood/expertiza/blob/master/client/src/redux/reducers/StudentTaskView.js.&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=Student_Task_View&amp;diff=125156</id>
		<title>Student Task View</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Student_Task_View&amp;diff=125156"/>
		<updated>2019-09-26T06:08:50Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: /* Redux */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Introduction ==&lt;br /&gt;
&lt;br /&gt;
This is the page you land on after you click on any of the tasks listed in the StudentTaskList view. Essentially, this is a page that helps you manage a particular task. It has a timeline with all the deadlines, links to pages for submissions, managing your team for that task, etc. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Rails ==&lt;br /&gt;
&lt;br /&gt;
The controller responsible for serving requests for this particular component can be found here https://github.com/ashwinrisbood/expertiza/blob/master/app/controllers/api/v1/student_task_controller.rb&lt;br /&gt;
The request is handled by the view action found in the code above. This action should return a json to the front-end with all the task related information of the the participant. The json that is rendered by this particular action is as below,&lt;br /&gt;
&lt;br /&gt;
[[File:ViewJson.PNG]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Redux ==&lt;br /&gt;
&lt;br /&gt;
The redux action making HTTP axios request to the Rails action specified above can be found under https://github.com/ashwinrisbood/expertiza/blob/master/client/src/redux/actions/StudentTaskView.js. This action makes a POST request as id as the parameter. The data received from the API is then passed on to the reducers to make changes to the state. The action is as follows,&lt;br /&gt;
&lt;br /&gt;
[[File:OnLoadAction.PNG]]&lt;br /&gt;
&lt;br /&gt;
There are multiple actions that are dispatched that make changes to different attributes of the state.&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=Student_Task_View&amp;diff=125155</id>
		<title>Student Task View</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Student_Task_View&amp;diff=125155"/>
		<updated>2019-09-26T06:07:22Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: /* Redux */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Introduction ==&lt;br /&gt;
&lt;br /&gt;
This is the page you land on after you click on any of the tasks listed in the StudentTaskList view. Essentially, this is a page that helps you manage a particular task. It has a timeline with all the deadlines, links to pages for submissions, managing your team for that task, etc. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Rails ==&lt;br /&gt;
&lt;br /&gt;
The controller responsible for serving requests for this particular component can be found here https://github.com/ashwinrisbood/expertiza/blob/master/app/controllers/api/v1/student_task_controller.rb&lt;br /&gt;
The request is handled by the view action found in the code above. This action should return a json to the front-end with all the task related information of the the participant. The json that is rendered by this particular action is as below,&lt;br /&gt;
&lt;br /&gt;
[[File:ViewJson.PNG]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Redux ==&lt;br /&gt;
&lt;br /&gt;
The redux action making HTTP axios request to the Rails action specified above can be found under https://github.com/ashwinrisbood/expertiza/blob/master/client/src/redux/actions/StudentTaskView.js. This action makes a POST request as id as the parameter. The data received from the API is then passed on to the reducers to make changes to the state. The action is as follows,&lt;br /&gt;
&lt;br /&gt;
[[File:OnLoadAction.PNG]]&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=File:OnLoadAction.PNG&amp;diff=125154</id>
		<title>File:OnLoadAction.PNG</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=File:OnLoadAction.PNG&amp;diff=125154"/>
		<updated>2019-09-26T06:06:51Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=Student_Task_View&amp;diff=125153</id>
		<title>Student Task View</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Student_Task_View&amp;diff=125153"/>
		<updated>2019-09-26T06:06:03Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: /* Redux */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Introduction ==&lt;br /&gt;
&lt;br /&gt;
This is the page you land on after you click on any of the tasks listed in the StudentTaskList view. Essentially, this is a page that helps you manage a particular task. It has a timeline with all the deadlines, links to pages for submissions, managing your team for that task, etc. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Rails ==&lt;br /&gt;
&lt;br /&gt;
The controller responsible for serving requests for this particular component can be found here https://github.com/ashwinrisbood/expertiza/blob/master/app/controllers/api/v1/student_task_controller.rb&lt;br /&gt;
The request is handled by the view action found in the code above. This action should return a json to the front-end with all the task related information of the the participant. The json that is rendered by this particular action is as below,&lt;br /&gt;
&lt;br /&gt;
[[File:ViewJson.PNG]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Redux ==&lt;br /&gt;
&lt;br /&gt;
The redux action making HTTP axios request to the Rails action specified above can be found under https://github.com/ashwinrisbood/expertiza/blob/master/client/src/redux/actions/StudentTaskView.js. This action makes a POST request as id as the parameter. The data received from the API is then passed on to the reducers to make changes to the state. The action is as follows,&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=Student_Task_View&amp;diff=125152</id>
		<title>Student Task View</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Student_Task_View&amp;diff=125152"/>
		<updated>2019-09-26T00:04:35Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: /* Rails */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Introduction ==&lt;br /&gt;
&lt;br /&gt;
This is the page you land on after you click on any of the tasks listed in the StudentTaskList view. Essentially, this is a page that helps you manage a particular task. It has a timeline with all the deadlines, links to pages for submissions, managing your team for that task, etc. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Rails ==&lt;br /&gt;
&lt;br /&gt;
The controller responsible for serving requests for this particular component can be found here https://github.com/ashwinrisbood/expertiza/blob/master/app/controllers/api/v1/student_task_controller.rb&lt;br /&gt;
The request is handled by the view action found in the code above. This action should return a json to the front-end with all the task related information of the the participant. The json that is rendered by this particular action is as below,&lt;br /&gt;
&lt;br /&gt;
[[File:ViewJson.PNG]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Redux ==&lt;br /&gt;
&lt;br /&gt;
The action making HTTP axios request to the Rails action specified above can be found under https://github.com/ashwinrisbood/expertiza/blob/master/client/src/redux/actions/StudentTaskView.js&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=File:ViewJson.PNG&amp;diff=125151</id>
		<title>File:ViewJson.PNG</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=File:ViewJson.PNG&amp;diff=125151"/>
		<updated>2019-09-25T23:31:44Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: uploaded a new version of &amp;amp;quot;File:ViewJson.PNG&amp;amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=Student_Task_View&amp;diff=125150</id>
		<title>Student Task View</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Student_Task_View&amp;diff=125150"/>
		<updated>2019-09-25T23:28:20Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: /* Rails */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Introduction ==&lt;br /&gt;
&lt;br /&gt;
This is the page you land on after you click on any of the tasks listed in the StudentTaskList view. Essentially, this is a page that helps you manage a particular task. It has a timeline with all the deadlines, links to pages for submissions, managing your team for that task, etc. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Rails ==&lt;br /&gt;
&lt;br /&gt;
The controller responsible for serving requests for this particular component can be found here https://github.com/ashwinrisbood/expertiza/blob/master/app/controllers/api/v1/student_task_controller.rb&lt;br /&gt;
The request is handled by the view action found in the code above. This action should return a json to the front-end with all the task related information of the the participant. The json that is rendered by this particular action is as below,&lt;br /&gt;
&lt;br /&gt;
[[File:ViewJson.PNG]]&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=File:ViewJson.PNG&amp;diff=125149</id>
		<title>File:ViewJson.PNG</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=File:ViewJson.PNG&amp;diff=125149"/>
		<updated>2019-09-25T23:27:54Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=Student_Task_View&amp;diff=125148</id>
		<title>Student Task View</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Student_Task_View&amp;diff=125148"/>
		<updated>2019-09-25T23:17:09Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: /* Rails */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Introduction ==&lt;br /&gt;
&lt;br /&gt;
This is the page you land on after you click on any of the tasks listed in the StudentTaskList view. Essentially, this is a page that helps you manage a particular task. It has a timeline with all the deadlines, links to pages for submissions, managing your team for that task, etc. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Rails ==&lt;br /&gt;
&lt;br /&gt;
The controller responsible for serving requests for this particular component can be found here https://github.com/ashwinrisbood/expertiza/blob/master/app/controllers/api/v1/student_task_controller.rb&lt;br /&gt;
The request is handled by the view action found in the code above. This action should return a json to the front-end with all the task related information of the the participant. The json that is rendered by this particular action is as below,&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=Student_Task_View&amp;diff=125147</id>
		<title>Student Task View</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Student_Task_View&amp;diff=125147"/>
		<updated>2019-09-25T23:11:18Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: /* Introduction */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Introduction ==&lt;br /&gt;
&lt;br /&gt;
This is the page you land on after you click on any of the tasks listed in the StudentTaskList view. Essentially, this is a page that helps you manage a particular task. It has a timeline with all the deadlines, links to pages for submissions, managing your team for that task, etc. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Rails ==&lt;br /&gt;
&lt;br /&gt;
The controller responsible for serving request for this particular component can be found here https://github.com/ashwinrisbood/expertiza/blob/master/app/controllers/api/v1/student_task_controller.rb&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=Student_Task_View&amp;diff=125146</id>
		<title>Student Task View</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Student_Task_View&amp;diff=125146"/>
		<updated>2019-09-25T22:54:22Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: /* Introduction */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Introduction ==&lt;br /&gt;
&lt;br /&gt;
This is the page you land on after you click on any of the tasks listed in the StudentTaskList view. Essentially, this page shows a timeline for a task and shows you your progress according to the timeline. It also has links to pages that help you manage your team, submit your work, etc.&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=Student_Task_View&amp;diff=125145</id>
		<title>Student Task View</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Student_Task_View&amp;diff=125145"/>
		<updated>2019-09-25T22:50:24Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: /* Introduction */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Introduction ==&lt;br /&gt;
&lt;br /&gt;
This is the page you land on after you click on any of the tasks listed in the StudentTaskList view. Essentially, this is what the page looks like,&lt;br /&gt;
&lt;br /&gt;
[[File:TaskView.PNG]]&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=File:TaskView.PNG&amp;diff=125144</id>
		<title>File:TaskView.PNG</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=File:TaskView.PNG&amp;diff=125144"/>
		<updated>2019-09-25T22:49:48Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=Student_Task_View&amp;diff=125143</id>
		<title>Student Task View</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Student_Task_View&amp;diff=125143"/>
		<updated>2019-09-25T22:49:14Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: Created page with &amp;quot;== Introduction ==  This is the page you land on after you click on any of the tasks listed in the StudentTaskList view. Essentially, this is what the page looks like,&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Introduction ==&lt;br /&gt;
&lt;br /&gt;
This is the page you land on after you click on any of the tasks listed in the StudentTaskList view. Essentially, this is what the page looks like,&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=Front-End/Back-End&amp;diff=125142</id>
		<title>Front-End/Back-End</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Front-End/Back-End&amp;diff=125142"/>
		<updated>2019-09-25T22:39:04Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* [[Architecture and setup]]&lt;br /&gt;
&lt;br /&gt;
* [[Login Component]]&lt;br /&gt;
&lt;br /&gt;
* [[Student Tasks Component]]&lt;br /&gt;
&lt;br /&gt;
* [[Profile Component]]&lt;br /&gt;
&lt;br /&gt;
* [[Student Task View]]&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=Profile_Component&amp;diff=125141</id>
		<title>Profile Component</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Profile_Component&amp;diff=125141"/>
		<updated>2019-09-05T08:14:41Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: /* Rails */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Rails ==&lt;br /&gt;
&lt;br /&gt;
The code for the new Profile controller can be found here https://github.com/ashwinrisbood/expertiza/blob/master/client/src/redux/actions/Profile.js. The controller has an index and an update action for the corresponding get and put HTTP requests. When the profile component loads in react, axios call is made to the index action in the back-end for fetching the profile of the student who has logged in.&lt;br /&gt;
&lt;br /&gt;
[[File:ProfileIndex.PNG]]&lt;br /&gt;
&lt;br /&gt;
The update action is as follows,&lt;br /&gt;
&lt;br /&gt;
[[File:ProfileUpdate.PNG]]&lt;br /&gt;
&lt;br /&gt;
== Redux ==&lt;br /&gt;
&lt;br /&gt;
The redux actions for the Profile component can be found here https://github.com/ashwinrisbood/expertiza/blob/master/client/src/redux/actions/Profile.js. To fetch the current profile of the user axios get request is made to the Profile controller. The response is then passed on to the reducer to make changes to the state of the application. If any updates are made to the profile, the changes are passed on to the back-end using HTTP put request. Following is the code for both these actions,&lt;br /&gt;
&lt;br /&gt;
[[File:fetchProfile.PNG]]&lt;br /&gt;
&lt;br /&gt;
[[File:editProfile.PNG]]&lt;br /&gt;
&lt;br /&gt;
The reducer for this component can be found here https://github.com/ashwinrisbood/expertiza/blob/master/client/src/redux/reducers/Profile.js.&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=Profile_Component&amp;diff=125140</id>
		<title>Profile Component</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Profile_Component&amp;diff=125140"/>
		<updated>2019-09-05T08:03:47Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: /* Redux */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Rails ==&lt;br /&gt;
&lt;br /&gt;
The code for the new Profile controller can be found here https://github.com/ashwinrisbood/expertiza/blob/master/client/src/redux/actions/Profile.js. The controller has an index and update actions for the corresponding get and put HTTP requests. When the profile component loads in react, axios call is made to the index action in the back-end for fetching the profile of the student who has logged in.&lt;br /&gt;
&lt;br /&gt;
[[File:ProfileIndex.PNG]]&lt;br /&gt;
&lt;br /&gt;
The update action is as follows,&lt;br /&gt;
&lt;br /&gt;
[[File:ProfileUpdate.PNG]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Redux ==&lt;br /&gt;
&lt;br /&gt;
The redux actions for the Profile component can be found here https://github.com/ashwinrisbood/expertiza/blob/master/client/src/redux/actions/Profile.js. To fetch the current profile of the user axios get request is made to the Profile controller. The response is then passed on to the reducer to make changes to the state of the application. If any updates are made to the profile, the changes are passed on to the back-end using HTTP put request. Following is the code for both these actions,&lt;br /&gt;
&lt;br /&gt;
[[File:fetchProfile.PNG]]&lt;br /&gt;
&lt;br /&gt;
[[File:editProfile.PNG]]&lt;br /&gt;
&lt;br /&gt;
The reducer for this component can be found here https://github.com/ashwinrisbood/expertiza/blob/master/client/src/redux/reducers/Profile.js.&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=Profile_Component&amp;diff=125139</id>
		<title>Profile Component</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Profile_Component&amp;diff=125139"/>
		<updated>2019-09-05T08:01:08Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: /* Redux */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Rails ==&lt;br /&gt;
&lt;br /&gt;
The code for the new Profile controller can be found here https://github.com/ashwinrisbood/expertiza/blob/master/client/src/redux/actions/Profile.js. The controller has an index and update actions for the corresponding get and put HTTP requests. When the profile component loads in react, axios call is made to the index action in the back-end for fetching the profile of the student who has logged in.&lt;br /&gt;
&lt;br /&gt;
[[File:ProfileIndex.PNG]]&lt;br /&gt;
&lt;br /&gt;
The update action is as follows,&lt;br /&gt;
&lt;br /&gt;
[[File:ProfileUpdate.PNG]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Redux ==&lt;br /&gt;
&lt;br /&gt;
The redux actions for the Profile component can be found here https://github.com/ashwinrisbood/expertiza/blob/master/client/src/redux/actions/Profile.js. To fetch the current profile of the user axios get request is made to the Profile controller. The response is then passed on to the reducer to make changes to the state of the application. If any updates are made to the profile, the changes are passed on to the back-end using HTTP put request. Following is the code for both these actions,&lt;br /&gt;
&lt;br /&gt;
[[File:fetchProfile.PNG]]&lt;br /&gt;
&lt;br /&gt;
[[File:editProfile.PNG]]&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=File:EditProfile.PNG&amp;diff=125138</id>
		<title>File:EditProfile.PNG</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=File:EditProfile.PNG&amp;diff=125138"/>
		<updated>2019-09-05T08:00:26Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=File:FetchProfile.PNG&amp;diff=125137</id>
		<title>File:FetchProfile.PNG</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=File:FetchProfile.PNG&amp;diff=125137"/>
		<updated>2019-09-05T08:00:15Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=Profile_Component&amp;diff=125136</id>
		<title>Profile Component</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Profile_Component&amp;diff=125136"/>
		<updated>2019-09-05T07:55:03Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: /* Redux */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Rails ==&lt;br /&gt;
&lt;br /&gt;
The code for the new Profile controller can be found here https://github.com/ashwinrisbood/expertiza/blob/master/client/src/redux/actions/Profile.js. The controller has an index and update actions for the corresponding get and put HTTP requests. When the profile component loads in react, axios call is made to the index action in the back-end for fetching the profile of the student who has logged in.&lt;br /&gt;
&lt;br /&gt;
[[File:ProfileIndex.PNG]]&lt;br /&gt;
&lt;br /&gt;
The update action is as follows,&lt;br /&gt;
&lt;br /&gt;
[[File:ProfileUpdate.PNG]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Redux ==&lt;br /&gt;
&lt;br /&gt;
The redux actions for the Profile component can be found here https://github.com/ashwinrisbood/expertiza/blob/master/client/src/redux/actions/Profile.js. To fetch the current profile of the user axios get request is made to the Profile controller. The response is then passed on to the reducer to make changes to the state of the application. If any updates are made to the profile, the changes are passed on to the back-end using HTTP put request. Following is the code for both these actions,&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=Profile_Component&amp;diff=125135</id>
		<title>Profile Component</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Profile_Component&amp;diff=125135"/>
		<updated>2019-09-05T07:54:23Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: /* Rails */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Rails ==&lt;br /&gt;
&lt;br /&gt;
The code for the new Profile controller can be found here https://github.com/ashwinrisbood/expertiza/blob/master/client/src/redux/actions/Profile.js. The controller has an index and update actions for the corresponding get and put HTTP requests. When the profile component loads in react, axios call is made to the index action in the back-end for fetching the profile of the student who has logged in.&lt;br /&gt;
&lt;br /&gt;
[[File:ProfileIndex.PNG]]&lt;br /&gt;
&lt;br /&gt;
The update action is as follows,&lt;br /&gt;
&lt;br /&gt;
[[File:ProfileUpdate.PNG]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Redux ==&lt;br /&gt;
&lt;br /&gt;
The redux axtions for the Profile component can be found here expertiza/client/src/redux/actions/Profile.js. To fetch the current profile of the user axios get request is made to the Profile controller. The response is then passed on to the reducer to make changes to the state of the application. If any updates are made to the profile, the changes are passed on to the back-end using HTTP put request. Following is the code for both these actions,&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=Profile_Component&amp;diff=125134</id>
		<title>Profile Component</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Profile_Component&amp;diff=125134"/>
		<updated>2019-09-05T06:37:29Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: /* Rails */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Rails ==&lt;br /&gt;
&lt;br /&gt;
The code for the new Profile controller can be found here https://github.com/ashwinrisbood/expertiza/blob/master/client/src/redux/actions/Profile.js. The controller has an index and update actions for the corresponding get and put HTTP requests. When the profile component loads in react, axios call is made to the index action in the back-end for fetching the profile of the student who has logged in.&lt;br /&gt;
&lt;br /&gt;
[[File:ProfileIndex.PNG]]&lt;br /&gt;
&lt;br /&gt;
The update action is as follows,&lt;br /&gt;
&lt;br /&gt;
[[File:ProfileUpdate.PNG]]&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=File:ProfileUpdate.PNG&amp;diff=125133</id>
		<title>File:ProfileUpdate.PNG</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=File:ProfileUpdate.PNG&amp;diff=125133"/>
		<updated>2019-09-05T06:36:51Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=Profile_Component&amp;diff=125132</id>
		<title>Profile Component</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Profile_Component&amp;diff=125132"/>
		<updated>2019-09-05T06:36:36Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: /* Rails */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Rails ==&lt;br /&gt;
&lt;br /&gt;
The code for the new Profile controller can be found here https://github.com/ashwinrisbood/expertiza/blob/master/client/src/redux/actions/Profile.js. The controller has an index and update actions for the corresponding get and put HTTP requests. When the profile component loads in react, axios call is made to the index action in the back-end for fetching the profile of the student who has logged in.&lt;br /&gt;
&lt;br /&gt;
[[File:ProfileIndex.PNG]]&lt;br /&gt;
&lt;br /&gt;
The update action is as follows,&lt;br /&gt;
&lt;br /&gt;
[[File:Example.jpg]]&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=Profile_Component&amp;diff=125131</id>
		<title>Profile Component</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Profile_Component&amp;diff=125131"/>
		<updated>2019-09-05T06:09:32Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: /* Rails */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Rails ==&lt;br /&gt;
&lt;br /&gt;
The code for the new Profile controller can be found here https://github.com/ashwinrisbood/expertiza/blob/master/client/src/redux/actions/Profile.js. The controller has an index and update actions for the corresponding get and put HTTP requests. When the profile component loads in react, axios call is made to the index action in the back-end for fetching the profile of the student who has logged in.&lt;br /&gt;
&lt;br /&gt;
[[File:ProfileIndex.PNG]]&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=File:ProfileIndex.PNG&amp;diff=125130</id>
		<title>File:ProfileIndex.PNG</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=File:ProfileIndex.PNG&amp;diff=125130"/>
		<updated>2019-09-05T06:09:05Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=Profile_Component&amp;diff=125129</id>
		<title>Profile Component</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Profile_Component&amp;diff=125129"/>
		<updated>2019-09-05T05:40:23Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: /* Rails */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Rails ==&lt;br /&gt;
&lt;br /&gt;
The code for the new Profile controller can be found here https://github.com/ashwinrisbood/expertiza/blob/master/client/src/redux/actions/Profile.js. The controller has an index and update actions for the corresponding get and put HTTP requests. When the profile component loads in react, axios call is made to the index action in the back-end for fetching the profile of the student who has logged in.&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=Profile_Component&amp;diff=125128</id>
		<title>Profile Component</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Profile_Component&amp;diff=125128"/>
		<updated>2019-09-05T05:38:10Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: Created page with &amp;quot;== Rails ==  The code for the new Profile controller can be found here https://github.com/ashwinrisbood/expertiza/blob/master/client/src/redux/actions/Profile.js.&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Rails ==&lt;br /&gt;
&lt;br /&gt;
The code for the new Profile controller can be found here https://github.com/ashwinrisbood/expertiza/blob/master/client/src/redux/actions/Profile.js.&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=Front-End/Back-End&amp;diff=125127</id>
		<title>Front-End/Back-End</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Front-End/Back-End&amp;diff=125127"/>
		<updated>2019-09-05T05:29:41Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* [[Architecture and setup]]&lt;br /&gt;
&lt;br /&gt;
* [[Login Component]]&lt;br /&gt;
&lt;br /&gt;
* [[Student Tasks Component]]&lt;br /&gt;
&lt;br /&gt;
* [[Profile Component]]&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=Student_Tasks_Component&amp;diff=125122</id>
		<title>Student Tasks Component</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Student_Tasks_Component&amp;diff=125122"/>
		<updated>2019-08-21T20:24:26Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: /* Introduction */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Introduction ==&lt;br /&gt;
&lt;br /&gt;
After a student logs into Expertiza, the page that a student lands up on is the student tasks list, which as the name suggests lists the tasks the student has. The controller we are concerned with for procuring a list of such tasks is the &amp;lt;b&amp;gt;student_task_controller.rb&amp;lt;/b&amp;gt;, which has a method called &amp;lt;b&amp;gt;list&amp;lt;/b&amp;gt; which will provide us with a JSON object listing all the tasks.&lt;br /&gt;
&lt;br /&gt;
== Rails ==&lt;br /&gt;
&lt;br /&gt;
The logic from the original student_task_controller.rb controller and expertiza/app/views/student_task/list.html.erb view is replicated to our new API only controller. The list method in our new controller api/v1/student_task_controller.rb renders a JSON which consists of things shown in the picture below,&lt;br /&gt;
&lt;br /&gt;
[[File:Student_task_list.PNG]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The JSON contents student_task_to_json, tasks_to_json and revisions_to_json are composed of the following things,&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Student_task_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
[[File:Tasks_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
[[File:Revisions_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
== Redux ==&lt;br /&gt;
&lt;br /&gt;
The redux actions for StudentTaskList component can be found in &amp;lt;b&amp;gt;client/src/redux/actions/StudentTaskList.js&amp;lt;/b&amp;gt;. Here axios call is made to the student_task_controller's &amp;lt;b&amp;gt;list&amp;lt;/b&amp;gt; action. The response that is received is passed on to the appropriate reducers for making changes to the state. Following is the code for how the request is made and what is done with the received response.&lt;br /&gt;
&lt;br /&gt;
[[File:student_task_list_redux_action.PNG]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The reducer for the same can be found under expertiza/client/src/redux/reducers/StudentTaskList.js. The response that is received from the back-end has the following data which is present as different data structures depending upon how the json was formulated in the back-end,&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;studentsTeamedWith&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;studentTasks&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;teamCourse&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;tasks_not_started&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;taskRevisions&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;hasTopics&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;hasBadges&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the reducer, depending upon the action, which is determined by the response data received, following changes are appended to the state of the client application,&lt;br /&gt;
&lt;br /&gt;
[[File:student_task_list_reducer.PNG]]&lt;br /&gt;
&lt;br /&gt;
== React ==&lt;br /&gt;
&lt;br /&gt;
The state data is passed to &amp;lt;b&amp;gt;studentList&amp;lt;/b&amp;gt; react component as props from the main component. This is the code you will find in the main component,&lt;br /&gt;
&lt;br /&gt;
[[File:routeToList.PNG]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In the StudentList React component, which is found under &amp;lt;b&amp;gt;client/src/components/studentList/StudentList.js&amp;lt;/b&amp;gt;, the props received are mapped to the component state and the page is populated accordingly.&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=Student_Tasks_Component&amp;diff=125121</id>
		<title>Student Tasks Component</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Student_Tasks_Component&amp;diff=125121"/>
		<updated>2019-08-21T07:22:32Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: /* React */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Introduction ==&lt;br /&gt;
&lt;br /&gt;
After a student logs into Expertiza, the page that the student lands up on is the student tasks list, which as the name suggests lists the tasks the student has. The controller we are concerned with for procuring a list of such tasks is the &amp;lt;b&amp;gt;student_task_controller.rb&amp;lt;/b&amp;gt;, which has a method called &amp;lt;b&amp;gt;list&amp;lt;/b&amp;gt; which will provide us with a JSON object listing all the tasks.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Rails ==&lt;br /&gt;
&lt;br /&gt;
The logic from the original student_task_controller.rb controller and expertiza/app/views/student_task/list.html.erb view is replicated to our new API only controller. The list method in our new controller api/v1/student_task_controller.rb renders a JSON which consists of things shown in the picture below,&lt;br /&gt;
&lt;br /&gt;
[[File:Student_task_list.PNG]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The JSON contents student_task_to_json, tasks_to_json and revisions_to_json are composed of the following things,&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Student_task_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
[[File:Tasks_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
[[File:Revisions_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
== Redux ==&lt;br /&gt;
&lt;br /&gt;
The redux actions for StudentTaskList component can be found in &amp;lt;b&amp;gt;client/src/redux/actions/StudentTaskList.js&amp;lt;/b&amp;gt;. Here axios call is made to the student_task_controller's &amp;lt;b&amp;gt;list&amp;lt;/b&amp;gt; action. The response that is received is passed on to the appropriate reducers for making changes to the state. Following is the code for how the request is made and what is done with the received response.&lt;br /&gt;
&lt;br /&gt;
[[File:student_task_list_redux_action.PNG]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The reducer for the same can be found under expertiza/client/src/redux/reducers/StudentTaskList.js. The response that is received from the back-end has the following data which is present as different data structures depending upon how the json was formulated in the back-end,&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;studentsTeamedWith&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;studentTasks&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;teamCourse&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;tasks_not_started&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;taskRevisions&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;hasTopics&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;hasBadges&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the reducer, depending upon the action, which is determined by the response data received, following changes are appended to the state of the client application,&lt;br /&gt;
&lt;br /&gt;
[[File:student_task_list_reducer.PNG]]&lt;br /&gt;
&lt;br /&gt;
== React ==&lt;br /&gt;
&lt;br /&gt;
The state data is passed to &amp;lt;b&amp;gt;studentList&amp;lt;/b&amp;gt; react component as props from the main component. This is the code you will find in the main component,&lt;br /&gt;
&lt;br /&gt;
[[File:routeToList.PNG]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In the StudentList React component, which is found under &amp;lt;b&amp;gt;client/src/components/studentList/StudentList.js&amp;lt;/b&amp;gt;, the props received are mapped to the component state and the page is populated accordingly.&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=Student_Tasks_Component&amp;diff=125120</id>
		<title>Student Tasks Component</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Student_Tasks_Component&amp;diff=125120"/>
		<updated>2019-08-21T07:18:55Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: /* React */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Introduction ==&lt;br /&gt;
&lt;br /&gt;
After a student logs into Expertiza, the page that the student lands up on is the student tasks list, which as the name suggests lists the tasks the student has. The controller we are concerned with for procuring a list of such tasks is the &amp;lt;b&amp;gt;student_task_controller.rb&amp;lt;/b&amp;gt;, which has a method called &amp;lt;b&amp;gt;list&amp;lt;/b&amp;gt; which will provide us with a JSON object listing all the tasks.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Rails ==&lt;br /&gt;
&lt;br /&gt;
The logic from the original student_task_controller.rb controller and expertiza/app/views/student_task/list.html.erb view is replicated to our new API only controller. The list method in our new controller api/v1/student_task_controller.rb renders a JSON which consists of things shown in the picture below,&lt;br /&gt;
&lt;br /&gt;
[[File:Student_task_list.PNG]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The JSON contents student_task_to_json, tasks_to_json and revisions_to_json are composed of the following things,&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Student_task_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
[[File:Tasks_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
[[File:Revisions_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
== Redux ==&lt;br /&gt;
&lt;br /&gt;
The redux actions for StudentTaskList component can be found in &amp;lt;b&amp;gt;client/src/redux/actions/StudentTaskList.js&amp;lt;/b&amp;gt;. Here axios call is made to the student_task_controller's &amp;lt;b&amp;gt;list&amp;lt;/b&amp;gt; action. The response that is received is passed on to the appropriate reducers for making changes to the state. Following is the code for how the request is made and what is done with the received response.&lt;br /&gt;
&lt;br /&gt;
[[File:student_task_list_redux_action.PNG]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The reducer for the same can be found under expertiza/client/src/redux/reducers/StudentTaskList.js. The response that is received from the back-end has the following data which is present as different data structures depending upon how the json was formulated in the back-end,&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;studentsTeamedWith&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;studentTasks&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;teamCourse&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;tasks_not_started&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;taskRevisions&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;hasTopics&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;hasBadges&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the reducer, depending upon the action, which is determined by the response data received, following changes are appended to the state of the client application,&lt;br /&gt;
&lt;br /&gt;
[[File:student_task_list_reducer.PNG]]&lt;br /&gt;
&lt;br /&gt;
== React ==&lt;br /&gt;
&lt;br /&gt;
The state data is passed to &amp;lt;b&amp;gt;studentList&amp;lt;/b&amp;gt; react component as props from the main component. This is the code you will find in the main component,&lt;br /&gt;
&lt;br /&gt;
[[File:routeToList.PNG]]&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=File:RouteToList.PNG&amp;diff=125119</id>
		<title>File:RouteToList.PNG</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=File:RouteToList.PNG&amp;diff=125119"/>
		<updated>2019-08-21T07:18:13Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=Student_Tasks_Component&amp;diff=125118</id>
		<title>Student Tasks Component</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Student_Tasks_Component&amp;diff=125118"/>
		<updated>2019-08-21T07:17:45Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: /* React */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Introduction ==&lt;br /&gt;
&lt;br /&gt;
After a student logs into Expertiza, the page that the student lands up on is the student tasks list, which as the name suggests lists the tasks the student has. The controller we are concerned with for procuring a list of such tasks is the &amp;lt;b&amp;gt;student_task_controller.rb&amp;lt;/b&amp;gt;, which has a method called &amp;lt;b&amp;gt;list&amp;lt;/b&amp;gt; which will provide us with a JSON object listing all the tasks.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Rails ==&lt;br /&gt;
&lt;br /&gt;
The logic from the original student_task_controller.rb controller and expertiza/app/views/student_task/list.html.erb view is replicated to our new API only controller. The list method in our new controller api/v1/student_task_controller.rb renders a JSON which consists of things shown in the picture below,&lt;br /&gt;
&lt;br /&gt;
[[File:Student_task_list.PNG]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The JSON contents student_task_to_json, tasks_to_json and revisions_to_json are composed of the following things,&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Student_task_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
[[File:Tasks_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
[[File:Revisions_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
== Redux ==&lt;br /&gt;
&lt;br /&gt;
The redux actions for StudentTaskList component can be found in &amp;lt;b&amp;gt;client/src/redux/actions/StudentTaskList.js&amp;lt;/b&amp;gt;. Here axios call is made to the student_task_controller's &amp;lt;b&amp;gt;list&amp;lt;/b&amp;gt; action. The response that is received is passed on to the appropriate reducers for making changes to the state. Following is the code for how the request is made and what is done with the received response.&lt;br /&gt;
&lt;br /&gt;
[[File:student_task_list_redux_action.PNG]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The reducer for the same can be found under expertiza/client/src/redux/reducers/StudentTaskList.js. The response that is received from the back-end has the following data which is present as different data structures depending upon how the json was formulated in the back-end,&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;studentsTeamedWith&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;studentTasks&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;teamCourse&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;tasks_not_started&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;taskRevisions&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;hasTopics&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;hasBadges&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the reducer, depending upon the action, which is determined by the response data received, following changes are appended to the state of the client application,&lt;br /&gt;
&lt;br /&gt;
[[File:student_task_list_reducer.PNG]]&lt;br /&gt;
&lt;br /&gt;
== React ==&lt;br /&gt;
&lt;br /&gt;
The state data is passed to &amp;lt;b&amp;gt;studentList&amp;lt;/b&amp;gt; react component as props from the main component. This is the code you will find in the main component,&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=Student_Tasks_Component&amp;diff=125117</id>
		<title>Student Tasks Component</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Student_Tasks_Component&amp;diff=125117"/>
		<updated>2019-08-21T06:32:17Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: /* Redux */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Introduction ==&lt;br /&gt;
&lt;br /&gt;
After a student logs into Expertiza, the page that the student lands up on is the student tasks list, which as the name suggests lists the tasks the student has. The controller we are concerned with for procuring a list of such tasks is the &amp;lt;b&amp;gt;student_task_controller.rb&amp;lt;/b&amp;gt;, which has a method called &amp;lt;b&amp;gt;list&amp;lt;/b&amp;gt; which will provide us with a JSON object listing all the tasks.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Rails ==&lt;br /&gt;
&lt;br /&gt;
The logic from the original student_task_controller.rb controller and expertiza/app/views/student_task/list.html.erb view is replicated to our new API only controller. The list method in our new controller api/v1/student_task_controller.rb renders a JSON which consists of things shown in the picture below,&lt;br /&gt;
&lt;br /&gt;
[[File:Student_task_list.PNG]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The JSON contents student_task_to_json, tasks_to_json and revisions_to_json are composed of the following things,&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Student_task_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
[[File:Tasks_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
[[File:Revisions_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
== Redux ==&lt;br /&gt;
&lt;br /&gt;
The redux actions for StudentTaskList component can be found in &amp;lt;b&amp;gt;client/src/redux/actions/StudentTaskList.js&amp;lt;/b&amp;gt;. Here axios call is made to the student_task_controller's &amp;lt;b&amp;gt;list&amp;lt;/b&amp;gt; action. The response that is received is passed on to the appropriate reducers for making changes to the state. Following is the code for how the request is made and what is done with the received response.&lt;br /&gt;
&lt;br /&gt;
[[File:student_task_list_redux_action.PNG]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The reducer for the same can be found under expertiza/client/src/redux/reducers/StudentTaskList.js. The response that is received from the back-end has the following data which is present as different data structures depending upon how the json was formulated in the back-end,&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;studentsTeamedWith&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;studentTasks&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;teamCourse&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;tasks_not_started&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;taskRevisions&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;hasTopics&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;hasBadges&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the reducer, depending upon the action, which is determined by the response data received, following changes are appended to the state of the client application,&lt;br /&gt;
&lt;br /&gt;
[[File:student_task_list_reducer.PNG]]&lt;br /&gt;
&lt;br /&gt;
== React ==&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=File:Student_task_list_reducer.PNG&amp;diff=125116</id>
		<title>File:Student task list reducer.PNG</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=File:Student_task_list_reducer.PNG&amp;diff=125116"/>
		<updated>2019-08-21T06:31:44Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=Student_Tasks_Component&amp;diff=125115</id>
		<title>Student Tasks Component</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Student_Tasks_Component&amp;diff=125115"/>
		<updated>2019-08-21T06:31:10Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: /* Redux */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Introduction ==&lt;br /&gt;
&lt;br /&gt;
After a student logs into Expertiza, the page that the student lands up on is the student tasks list, which as the name suggests lists the tasks the student has. The controller we are concerned with for procuring a list of such tasks is the &amp;lt;b&amp;gt;student_task_controller.rb&amp;lt;/b&amp;gt;, which has a method called &amp;lt;b&amp;gt;list&amp;lt;/b&amp;gt; which will provide us with a JSON object listing all the tasks.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Rails ==&lt;br /&gt;
&lt;br /&gt;
The logic from the original student_task_controller.rb controller and expertiza/app/views/student_task/list.html.erb view is replicated to our new API only controller. The list method in our new controller api/v1/student_task_controller.rb renders a JSON which consists of things shown in the picture below,&lt;br /&gt;
&lt;br /&gt;
[[File:Student_task_list.PNG]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The JSON contents student_task_to_json, tasks_to_json and revisions_to_json are composed of the following things,&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Student_task_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
[[File:Tasks_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
[[File:Revisions_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
== Redux ==&lt;br /&gt;
&lt;br /&gt;
The redux actions for StudentTaskList component can be found in &amp;lt;b&amp;gt;client/src/redux/actions/StudentTaskList.js&amp;lt;/b&amp;gt;. Here axios call is made to the student_task_controller's &amp;lt;b&amp;gt;list&amp;lt;/b&amp;gt; action. The response that is received is passed on to the appropriate reducers for making changes to the state. Following is the code for how the request is made and what is done with the received response.&lt;br /&gt;
&lt;br /&gt;
[[File:student_task_list_redux_action.PNG]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The reducer for the same can be found under expertiza/client/src/redux/reducers/StudentTaskList.js. The response that is received from the back-end has the following data which is present as different data structures depending upon how the json was formulated in the back-end,&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;studentsTeamedWith&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;studentTasks&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;teamCourse&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;tasks_not_started&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;taskRevisions&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;hasTopics&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;hasBadges&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the reducer, depending upon the action, which is determined by the response data received, following changes are appended to the state of the client application,&lt;br /&gt;
&lt;br /&gt;
== React ==&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=Student_Tasks_Component&amp;diff=125114</id>
		<title>Student Tasks Component</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Student_Tasks_Component&amp;diff=125114"/>
		<updated>2019-08-21T06:27:17Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: /* Redux */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Introduction ==&lt;br /&gt;
&lt;br /&gt;
After a student logs into Expertiza, the page that the student lands up on is the student tasks list, which as the name suggests lists the tasks the student has. The controller we are concerned with for procuring a list of such tasks is the &amp;lt;b&amp;gt;student_task_controller.rb&amp;lt;/b&amp;gt;, which has a method called &amp;lt;b&amp;gt;list&amp;lt;/b&amp;gt; which will provide us with a JSON object listing all the tasks.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Rails ==&lt;br /&gt;
&lt;br /&gt;
The logic from the original student_task_controller.rb controller and expertiza/app/views/student_task/list.html.erb view is replicated to our new API only controller. The list method in our new controller api/v1/student_task_controller.rb renders a JSON which consists of things shown in the picture below,&lt;br /&gt;
&lt;br /&gt;
[[File:Student_task_list.PNG]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The JSON contents student_task_to_json, tasks_to_json and revisions_to_json are composed of the following things,&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Student_task_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
[[File:Tasks_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
[[File:Revisions_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
== Redux ==&lt;br /&gt;
&lt;br /&gt;
The redux actions for StudentTaskList component can be found in &amp;lt;b&amp;gt;client/src/redux/actions/StudentTaskList.js&amp;lt;/b&amp;gt;. Here axios call is made to the student_task_controller's &amp;lt;b&amp;gt;list&amp;lt;/b&amp;gt; action. The response that is received is passed on to the appropriate reducers for making changes to the state. Following is the code for how the request is made and what is done with the received response.&lt;br /&gt;
&lt;br /&gt;
[[File:student_task_list_redux_action.PNG]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The reducer for the same can be found under expertiza/client/src/redux/reducers/StudentTaskList.js. The response that is received from the back-end has the following data which is present as different data structures depending upon how the json was formulated in the back-end,&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;studentsTeamedWith&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;studentTasks&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;teamCourse&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;tasks_not_started&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;taskRevisions&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;hasTopics&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;hasBadges&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== React ==&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=Student_Tasks_Component&amp;diff=125113</id>
		<title>Student Tasks Component</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Student_Tasks_Component&amp;diff=125113"/>
		<updated>2019-08-21T06:25:36Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: /* Redux */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Introduction ==&lt;br /&gt;
&lt;br /&gt;
After a student logs into Expertiza, the page that the student lands up on is the student tasks list, which as the name suggests lists the tasks the student has. The controller we are concerned with for procuring a list of such tasks is the &amp;lt;b&amp;gt;student_task_controller.rb&amp;lt;/b&amp;gt;, which has a method called &amp;lt;b&amp;gt;list&amp;lt;/b&amp;gt; which will provide us with a JSON object listing all the tasks.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Rails ==&lt;br /&gt;
&lt;br /&gt;
The logic from the original student_task_controller.rb controller and expertiza/app/views/student_task/list.html.erb view is replicated to our new API only controller. The list method in our new controller api/v1/student_task_controller.rb renders a JSON which consists of things shown in the picture below,&lt;br /&gt;
&lt;br /&gt;
[[File:Student_task_list.PNG]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The JSON contents student_task_to_json, tasks_to_json and revisions_to_json are composed of the following things,&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Student_task_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
[[File:Tasks_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
[[File:Revisions_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
== Redux ==&lt;br /&gt;
&lt;br /&gt;
The redux actions for StudentTaskList component can be found in &amp;lt;b&amp;gt;client/src/redux/actions/StudentTaskList.js&amp;lt;/b&amp;gt;. Here axios call is made to the student_task_controller's &amp;lt;b&amp;gt;list&amp;lt;/b&amp;gt; action. The response that is received is passed on to the appropriate reducers for making changes to the state. Following is the code for how the request is made and what is done with the received response.&lt;br /&gt;
&lt;br /&gt;
[[File:student_task_list_redux_action.PNG]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The reducer for the same can be found under expertiza/client/src/redux/reducers/StudentTaskList.js. The response that is received from the back-end has the following data which is present as different data structures depending upon how the json was formulated in the back-end,&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; studentsTeamedWith &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== React ==&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=Student_Tasks_Component&amp;diff=125112</id>
		<title>Student Tasks Component</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Student_Tasks_Component&amp;diff=125112"/>
		<updated>2019-08-21T06:24:09Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: /* Redux */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Introduction ==&lt;br /&gt;
&lt;br /&gt;
After a student logs into Expertiza, the page that the student lands up on is the student tasks list, which as the name suggests lists the tasks the student has. The controller we are concerned with for procuring a list of such tasks is the &amp;lt;b&amp;gt;student_task_controller.rb&amp;lt;/b&amp;gt;, which has a method called &amp;lt;b&amp;gt;list&amp;lt;/b&amp;gt; which will provide us with a JSON object listing all the tasks.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Rails ==&lt;br /&gt;
&lt;br /&gt;
The logic from the original student_task_controller.rb controller and expertiza/app/views/student_task/list.html.erb view is replicated to our new API only controller. The list method in our new controller api/v1/student_task_controller.rb renders a JSON which consists of things shown in the picture below,&lt;br /&gt;
&lt;br /&gt;
[[File:Student_task_list.PNG]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The JSON contents student_task_to_json, tasks_to_json and revisions_to_json are composed of the following things,&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Student_task_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
[[File:Tasks_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
[[File:Revisions_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
== Redux ==&lt;br /&gt;
&lt;br /&gt;
The redux actions for StudentTaskList component can be found in &amp;lt;b&amp;gt;client/src/redux/actions/StudentTaskList.js&amp;lt;/b&amp;gt;. Here axios call is made to the student_task_controller's &amp;lt;b&amp;gt;list&amp;lt;/b&amp;gt; action. The response that is received is passed on to the appropriate reducers for making changes to the state. Following is the code for how the request is made and what is done with the received response.&lt;br /&gt;
&lt;br /&gt;
[[File:student_task_list_redux_action.PNG]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The reducer for the same can be found under expertiza/client/src/redux/reducers/StudentTaskList.js. The response that is received from the back-end has the following data which is present as different data structures depending upon how the json was formulated in the back-end,&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt; studentsTeamedWith &amp;lt;/li&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== React ==&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=Student_Tasks_Component&amp;diff=125111</id>
		<title>Student Tasks Component</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Student_Tasks_Component&amp;diff=125111"/>
		<updated>2019-08-21T06:23:36Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: /* Redux */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Introduction ==&lt;br /&gt;
&lt;br /&gt;
After a student logs into Expertiza, the page that the student lands up on is the student tasks list, which as the name suggests lists the tasks the student has. The controller we are concerned with for procuring a list of such tasks is the &amp;lt;b&amp;gt;student_task_controller.rb&amp;lt;/b&amp;gt;, which has a method called &amp;lt;b&amp;gt;list&amp;lt;/b&amp;gt; which will provide us with a JSON object listing all the tasks.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Rails ==&lt;br /&gt;
&lt;br /&gt;
The logic from the original student_task_controller.rb controller and expertiza/app/views/student_task/list.html.erb view is replicated to our new API only controller. The list method in our new controller api/v1/student_task_controller.rb renders a JSON which consists of things shown in the picture below,&lt;br /&gt;
&lt;br /&gt;
[[File:Student_task_list.PNG]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The JSON contents student_task_to_json, tasks_to_json and revisions_to_json are composed of the following things,&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Student_task_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
[[File:Tasks_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
[[File:Revisions_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
== Redux ==&lt;br /&gt;
&lt;br /&gt;
The redux actions for StudentTaskList component can be found in &amp;lt;b&amp;gt;client/src/redux/actions/StudentTaskList.js&amp;lt;/b&amp;gt;. Here axios call is made to the student_task_controller's &amp;lt;b&amp;gt;list&amp;lt;/b&amp;gt; action. The response that is received is passed on to the appropriate reducers for making changes to the state. Following is the code for how the request is made and what is done with the received response.&lt;br /&gt;
&lt;br /&gt;
[[File:student_task_list_redux_action.PNG]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The reducer for the same can be found under expertiza/client/src/redux/reducers/StudentTaskList.js. The response that is received from the back-end has the following data which is present as different data structures depending upon how the json was formulated in the back-end,&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;studentsTeamedWith&amp;lt;/li&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== React ==&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=Student_Tasks_Component&amp;diff=125110</id>
		<title>Student Tasks Component</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Student_Tasks_Component&amp;diff=125110"/>
		<updated>2019-08-21T06:12:38Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: /* Redux */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Introduction ==&lt;br /&gt;
&lt;br /&gt;
After a student logs into Expertiza, the page that the student lands up on is the student tasks list, which as the name suggests lists the tasks the student has. The controller we are concerned with for procuring a list of such tasks is the &amp;lt;b&amp;gt;student_task_controller.rb&amp;lt;/b&amp;gt;, which has a method called &amp;lt;b&amp;gt;list&amp;lt;/b&amp;gt; which will provide us with a JSON object listing all the tasks.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Rails ==&lt;br /&gt;
&lt;br /&gt;
The logic from the original student_task_controller.rb controller and expertiza/app/views/student_task/list.html.erb view is replicated to our new API only controller. The list method in our new controller api/v1/student_task_controller.rb renders a JSON which consists of things shown in the picture below,&lt;br /&gt;
&lt;br /&gt;
[[File:Student_task_list.PNG]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The JSON contents student_task_to_json, tasks_to_json and revisions_to_json are composed of the following things,&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Student_task_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
[[File:Tasks_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
[[File:Revisions_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
== Redux ==&lt;br /&gt;
&lt;br /&gt;
The redux actions for StudentTaskList component can be found in &amp;lt;b&amp;gt;client/src/redux/actions/StudentTaskList.js&amp;lt;/b&amp;gt;. Here axios call is made to the student_task_controller's &amp;lt;b&amp;gt;list&amp;lt;/b&amp;gt; action. The response that is received is passed on to the appropriate reducers for making changes to the state. Following is the code for how the request is made and what is done with the received response.&lt;br /&gt;
&lt;br /&gt;
[[File:student_task_list_redux_action.PNG]]&lt;br /&gt;
&lt;br /&gt;
== React ==&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=File:Student_task_list_redux_action.PNG&amp;diff=125109</id>
		<title>File:Student task list redux action.PNG</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=File:Student_task_list_redux_action.PNG&amp;diff=125109"/>
		<updated>2019-08-21T06:12:03Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=Student_Tasks_Component&amp;diff=125108</id>
		<title>Student Tasks Component</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Student_Tasks_Component&amp;diff=125108"/>
		<updated>2019-08-21T06:11:13Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: /* Redux */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Introduction ==&lt;br /&gt;
&lt;br /&gt;
After a student logs into Expertiza, the page that the student lands up on is the student tasks list, which as the name suggests lists the tasks the student has. The controller we are concerned with for procuring a list of such tasks is the &amp;lt;b&amp;gt;student_task_controller.rb&amp;lt;/b&amp;gt;, which has a method called &amp;lt;b&amp;gt;list&amp;lt;/b&amp;gt; which will provide us with a JSON object listing all the tasks.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Rails ==&lt;br /&gt;
&lt;br /&gt;
The logic from the original student_task_controller.rb controller and expertiza/app/views/student_task/list.html.erb view is replicated to our new API only controller. The list method in our new controller api/v1/student_task_controller.rb renders a JSON which consists of things shown in the picture below,&lt;br /&gt;
&lt;br /&gt;
[[File:Student_task_list.PNG]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The JSON contents student_task_to_json, tasks_to_json and revisions_to_json are composed of the following things,&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Student_task_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
[[File:Tasks_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
[[File:Revisions_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
== Redux ==&lt;br /&gt;
&lt;br /&gt;
The redux actions for StudentTaskList component can be found in &amp;lt;b&amp;gt;client/src/redux/actions/StudentTaskList.js&amp;lt;/b&amp;gt;. Here axios call is made to the student_task_controller's &amp;lt;b&amp;gt;list&amp;lt;/b&amp;gt; action. The response that is received is passed on to the appropriate reducers for making changes to the state. Following is the code for how the request is made and what is done with the received response.&lt;br /&gt;
&lt;br /&gt;
== React ==&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=Student_Tasks_Component&amp;diff=125107</id>
		<title>Student Tasks Component</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Student_Tasks_Component&amp;diff=125107"/>
		<updated>2019-08-21T06:10:49Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: /* Redux */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Introduction ==&lt;br /&gt;
&lt;br /&gt;
After a student logs into Expertiza, the page that the student lands up on is the student tasks list, which as the name suggests lists the tasks the student has. The controller we are concerned with for procuring a list of such tasks is the &amp;lt;b&amp;gt;student_task_controller.rb&amp;lt;/b&amp;gt;, which has a method called &amp;lt;b&amp;gt;list&amp;lt;/b&amp;gt; which will provide us with a JSON object listing all the tasks.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Rails ==&lt;br /&gt;
&lt;br /&gt;
The logic from the original student_task_controller.rb controller and expertiza/app/views/student_task/list.html.erb view is replicated to our new API only controller. The list method in our new controller api/v1/student_task_controller.rb renders a JSON which consists of things shown in the picture below,&lt;br /&gt;
&lt;br /&gt;
[[File:Student_task_list.PNG]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The JSON contents student_task_to_json, tasks_to_json and revisions_to_json are composed of the following things,&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Student_task_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
[[File:Tasks_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
[[File:Revisions_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
== Redux ==&lt;br /&gt;
&lt;br /&gt;
The redux actions for StudentTaskList component can be found in &amp;lt;b&amp;gt;client/src/redux/actions/StudentTaskList.js&amp;lt;/b&amp;gt;. Here axios call is made to the student_task_controller's &amp;lt;b&amp;gt;list&amp;lt;/b&amp;gt; action. The response that is received is passed on to the appropriate reducers for making changes to the state. Following is the code for how the request is made and what is done with the response received.&lt;br /&gt;
&lt;br /&gt;
== React ==&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=Student_Tasks_Component&amp;diff=125106</id>
		<title>Student Tasks Component</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Student_Tasks_Component&amp;diff=125106"/>
		<updated>2019-08-05T07:40:05Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: /* Redux */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Introduction ==&lt;br /&gt;
&lt;br /&gt;
After a student logs into Expertiza, the page that the student lands up on is the student tasks list, which as the name suggests lists the tasks the student has. The controller we are concerned with for procuring a list of such tasks is the &amp;lt;b&amp;gt;student_task_controller.rb&amp;lt;/b&amp;gt;, which has a method called &amp;lt;b&amp;gt;list&amp;lt;/b&amp;gt; which will provide us with a JSON object listing all the tasks.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Rails ==&lt;br /&gt;
&lt;br /&gt;
The logic from the original student_task_controller.rb controller and expertiza/app/views/student_task/list.html.erb view is replicated to our new API only controller. The list method in our new controller api/v1/student_task_controller.rb renders a JSON which consists of things shown in the picture below,&lt;br /&gt;
&lt;br /&gt;
[[File:Student_task_list.PNG]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The JSON contents student_task_to_json, tasks_to_json and revisions_to_json are composed of the following things,&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Student_task_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
[[File:Tasks_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
[[File:Revisions_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
== Redux ==&lt;br /&gt;
&lt;br /&gt;
== React ==&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=Student_Tasks_Component&amp;diff=125105</id>
		<title>Student Tasks Component</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Student_Tasks_Component&amp;diff=125105"/>
		<updated>2019-08-05T06:11:17Z</updated>

		<summary type="html">&lt;p&gt;Spoudwa: /* Rails */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Introduction ==&lt;br /&gt;
&lt;br /&gt;
After a student logs into Expertiza, the page that the student lands up on is the student tasks list, which as the name suggests lists the tasks the student has. The controller we are concerned with for procuring a list of such tasks is the &amp;lt;b&amp;gt;student_task_controller.rb&amp;lt;/b&amp;gt;, which has a method called &amp;lt;b&amp;gt;list&amp;lt;/b&amp;gt; which will provide us with a JSON object listing all the tasks.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Rails ==&lt;br /&gt;
&lt;br /&gt;
The logic from the original student_task_controller.rb controller and expertiza/app/views/student_task/list.html.erb view is replicated to our new API only controller. The list method in our new controller api/v1/student_task_controller.rb renders a JSON which consists of things shown in the picture below,&lt;br /&gt;
&lt;br /&gt;
[[File:Student_task_list.PNG]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The JSON contents student_task_to_json, tasks_to_json and revisions_to_json are composed of the following things,&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Student_task_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
[[File:Tasks_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
[[File:Revisions_to_json.PNG]]&lt;br /&gt;
&lt;br /&gt;
== Redux == &lt;br /&gt;
&lt;br /&gt;
== React ==&lt;/div&gt;</summary>
		<author><name>Spoudwa</name></author>
	</entry>
</feed>