feat(Peer Group): Add teacher endpoint to get PeerGroup info for activity

[hirokiterashima]

Changes

• Added new teacher endpoint /api/teacher/peer-group-info/RUN_ID/NODE_ID/COMPONENT_ID that will return PeerGroups and Workgroups that aren't in PeerGroups for the specified activity
• Requires database change: add periodId bigint field to peer_groups table

Test Prep

• add periodId column to peer_groups table: alter table peer_groups add column periodId bigint;

Test

• Log in as a teacher
• Make request to /api/teacher/peer-group-info/RUN_ID/NODE_ID/COMPONENT_ID
  • If valid runId/nodeId/componentId combination and teacher does not have permissions, should see AccessDenied
  • If invalid runId/nodeId/componentId combination, should throw error
  • If valid runId/nodeId/componentId combination and teacher has permissions, should return a map containing two objects:
    • "peerGroups": list of PeerGroups for the activity in the run
    • "workgroupsNotInPeerGroup": list of Workgroups that are not in a PeerGroup for the activity

Closes #57

[geoffreykwan]

Should we be sending the peerGroupActivity object with every peerGroup? It's duplicated for every peerGroup. Do we even need the peerGroupActivity information in the response?

{
	"peerGroups": [{
		"id": 39,
		"peerGroupActivity": {
			"id": 9,
			"nodeId": "node51",
			"componentId": "70ewf4mmov",
			"logic": "[{\"componentId\":\"sneu5vdrcr\",\"name\":\"maximizeSimilarIdeas\",\"nodeId\":\"node50\"}]",
			"logicThresholdCount": 3,
			"logicThresholdPercent": 100,
			"maxMembershipCount": 2,
			"logicNodeId": "node50",
			"logicComponentId": "sneu5vdrcr"
		},
		"members": [{
			"id": 235,
			"periodId": 306
		}, {
			"id": 234,
			"periodId": 306
		}],
		"periodId": 306
	}, {
		"id": 40,
		"peerGroupActivity": {
			"id": 9,
			"nodeId": "node51",
			"componentId": "70ewf4mmov",
			"logic": "[{\"componentId\":\"sneu5vdrcr\",\"name\":\"maximizeSimilarIdeas\",\"nodeId\":\"node50\"}]",
			"logicThresholdCount": 3,
			"logicThresholdPercent": 100,
			"maxMembershipCount": 2,
			"logicNodeId": "node50",
			"logicComponentId": "sneu5vdrcr"
		},
		"members": [{
			"id": 238,
			"periodId": 307
		}, {
			"id": 239,
			"periodId": 307
		}],
		"periodId": 307
	}],
	"workgroupsNotInPeerGroup": [{
		"id": 236,
		"periodId": 306
	}, {
		"id": 237,
		"periodId": 306
	}, {
		"id": 240,
		"periodId": 307
	}]
}

[hirokiterashima]

This is the default serialization output.

We can write a custom JSON serializer for PeerGroup where we remove the PeerGroupActivity field altogether. This serialization would apply to all GET requests to PeerGroup. Or should we keep just the PeerGroupActivity.id field in cases where we'd request PeerGroups for different PeerGroupActivities (e.g. "get all PeerGroups for run")?

{
  "id": 39,
  "peerGroupActivity": {
    "id": 9			
  },
 "members": [{
   "id": 235,
   ...
  }]
}   

[hirokiterashima]

@geoffreykwan as discussed, I removed PeerGroupActivity from PeerGroup serialization

[geoffreykwan]

Looks good.