It turns out we had the sufficient candidate model - there is always a json field. Now if the first info created with a json, the candidate will also have that json. However, if the json is not in the firstinfo but in a later info related to this candidate, the json would not automatically go into that candidate. This works as planed - the latest info might not be the recommended info.
However, in the future, we might want to implement a quick way to update the candidate. We shall provide two ways to update one candidate: 1. overwrite the entire candidate (already implemented); 2. overlay the candidate with additional fields (TODO).
It turns out we had the sufficient
candidatemodel - there is always ajsonfield. Now if the firstinfocreated with ajson, thecandidatewill also have thatjson. However, if thejsonis not in the firstinfobut in a laterinforelated to thiscandidate, thejsonwould not automatically go into thatcandidate. This works as planed - the latestinfomight not be the recommendedinfo.However, in the future, we might want to implement a quick way to update the
candidate. We shall provide two ways to update onecandidate: 1. overwrite the entirecandidate(already implemented); 2. overlay thecandidatewith additional fields (TODO).