fake_order_edit.json 4.8 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192
  1. {
  2. "result": 2,
  3. "sections": [
  4. {
  5. "title": "Update Action",
  6. "items": [
  7. {
  8. "type": 0,
  9. "title": "Order ID",
  10. "value": "AFS20180530001200"
  11. },
  12. {
  13. "type": 0,
  14. "title": "Dispatcher",
  15. "value": "Jack Li"
  16. },
  17. {
  18. "type": 0,
  19. "title": "Current Action",
  20. "value": "Delivered"
  21. },
  22. {
  23. "type": 1,
  24. "title": "File No.",
  25. "key": "file_no_0",
  26. "value": "AFS20180530001200",
  27. "scannable": true
  28. },
  29. {
  30. "type": 1,
  31. "title": "File No.",
  32. "key": "file_no_1",
  33. "value": "AFS20180530001200",
  34. "scannable": false
  35. },
  36. {
  37. "type": 2,
  38. "key": "instruction_0",
  39. "title": "Instruction",
  40. "value": "不同于一般的 bug,性能问题因为并没有统一的标准,而且与用户的机器环境相关性较大,所以往往是在产品上线后才被发现,也导致解决问题的周期很长。微信读书 1.3.0 版本之前,性能问题基本都来自于用户反馈(包括测试人员),受限于测试时间和用户反馈的积极性,性能问题往往到了比较严重的程度,开发人员才真正发现问题。\n\n但是,移动应用要保证良好的用户体验,产品在性能方面的表现极其重要。为了尽可能早、尽可能全面地收集产品的性能问题,就避免不了对产品做性能监控。我们主要从两个维度进行了监控"
  41. },
  42. {
  43. "type": 3,
  44. "key": "container_photo_0",
  45. "title": "Container Photo",
  46. "path": "photoPath"
  47. },
  48. {
  49. "type": 0,
  50. "title": "Order ID",
  51. "value": "AFS20180530001200"
  52. },
  53. {
  54. "type": 0,
  55. "title": "Dispatcher",
  56. "value": "Jack Li"
  57. },
  58. {
  59. "type": 0,
  60. "title": "Current Action",
  61. "value": "Delivered"
  62. },
  63. {
  64. "type": 1,
  65. "title": "File No.",
  66. "key": "file_no_2",
  67. "value": "AFS20180530001200",
  68. "scannable": true
  69. },
  70. {
  71. "type": 1,
  72. "title": "File No.",
  73. "key": "file_no_3",
  74. "value": "AFS20180530001200",
  75. "scannable": false
  76. },
  77. {
  78. "type": 2,
  79. "title": "Instruction",
  80. "key": "instruction_1",
  81. "value": "不同于一般的 bug,性能问题因为并没有统一的标准,而且与用户的机器环境相关性较大,所以往往是在产品上线后才被发现,也导致解决问题的周期很长。微信读书 1.3.0 版本之前,性能问题基本都来自于用户反馈(包括测试人员),受限于测试时间和用户反馈的积极性,性能问题往往到了比较严重的程度,开发人员才真正发现问题。\n\n但是,移动应用要保证良好的用户体验,产品在性能方面的表现极其重要。为了尽可能早、尽可能全面地收集产品的性能问题,就避免不了对产品做性能监控。我们主要从两个维度进行了监控"
  82. },
  83. {
  84. "type": 3,
  85. "key": "container_photo_1",
  86. "title": "Container Photo",
  87. "path": "photoPath"
  88. }
  89. ]
  90. }
  91. ]
  92. }