TL;DR.
Data returned by the backend should be JSON, and should look like something like this:
{
"id" : 233,
"title" : "Some Epic Circuit That Will Help The Mankind",
"progress" : 2,
"tags" : ["Share", "Public"],
"img": "BASE64 encoded image data",
"description" : "this is the long version of description: blablablablablablablablablabla",
"introduction" : "this is the short version of description: blabla",
"equations" : ["some MathJax equation", "another MathJax equation"],
"references": "some very long multi-line text",
"comments" : ["commenta", "commentb", "commentc"]
}Among these key-value pairs, tags and progress are used only in personal center and can be safely ignored in Bank.
Since the Core-Bank and the personal database in personal center share this interface, I suggest the route for this interface be sth like GET /data/circuit_detail/<int:id>.
TL;DR.
Data returned by the backend should be JSON, and should look like something like this:
{ "id" : 233, "title" : "Some Epic Circuit That Will Help The Mankind", "progress" : 2, "tags" : ["Share", "Public"], "img": "BASE64 encoded image data", "description" : "this is the long version of description: blablablablablablablablablabla", "introduction" : "this is the short version of description: blabla", "equations" : ["some MathJax equation", "another MathJax equation"], "references": "some very long multi-line text", "comments" : ["commenta", "commentb", "commentc"] }Among these key-value pairs,
tagsandprogressare used only in personal center and can be safely ignored in Bank.Since the Core-Bank and the personal database in personal center share this interface, I suggest the route for this interface be sth like
GET /data/circuit_detail/<int:id>.