boards.js 3.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112
  1. // This is the publication used to display the board list. We publish all the
  2. // non-archived boards:
  3. // 1. that the user is a member of
  4. // 2. the user has starred
  5. Meteor.publish('boards', function() {
  6. // Ensure that the user is connected. If it is not, we need to return an empty
  7. // array to tell the client to remove the previously published docs.
  8. if (!Match.test(this.userId, String))
  9. return [];
  10. // Defensive programming to verify that starredBoards has the expected
  11. // format -- since the field is in the `profile` a user can modify it.
  12. const {starredBoards = []} = Users.findOne(this.userId).profile;
  13. check(starredBoards, [String]);
  14. return Boards.find({
  15. archived: false,
  16. $or: [
  17. { members: { $elemMatch: { userId: this.userId, isActive: true }}},
  18. { _id: { $in: starredBoards } },
  19. ],
  20. }, {
  21. fields: {
  22. _id: 1,
  23. archived: 1,
  24. slug: 1,
  25. title: 1,
  26. description: 1,
  27. color: 1,
  28. members: 1,
  29. permission: 1,
  30. },
  31. });
  32. });
  33. Meteor.publish('archivedBoards', function() {
  34. if (!Match.test(this.userId, String))
  35. return [];
  36. return Boards.find({
  37. archived: true,
  38. members: {
  39. $elemMatch: {
  40. userId: this.userId,
  41. isAdmin: true,
  42. },
  43. },
  44. }, {
  45. fields: {
  46. _id: 1,
  47. archived: 1,
  48. slug: 1,
  49. title: 1,
  50. },
  51. });
  52. });
  53. Meteor.publishRelations('board', function(boardId) {
  54. check(boardId, String);
  55. this.cursor(Boards.find({
  56. _id: boardId,
  57. archived: false,
  58. // If the board is not public the user has to be a member of it to see
  59. // it.
  60. $or: [
  61. { permission: 'public' },
  62. { members: { $elemMatch: { userId: this.userId, isActive: true }}},
  63. ],
  64. }, { limit: 1 }), function(boardId, board) {
  65. this.cursor(Lists.find({ boardId }));
  66. // Cards and cards comments
  67. // XXX Originally we were publishing the card documents as a child of the
  68. // list publication defined above using the following selector `{ listId:
  69. // list._id }`. But it was causing a race condition in publish-composite,
  70. // that I documented here:
  71. //
  72. // https://github.com/englue/meteor-publish-composite/issues/29
  73. //
  74. // cottz:publish had a similar problem:
  75. //
  76. // https://github.com/Goluis/cottz-publish/issues/4
  77. //
  78. // The current state of relational publishing in meteor is a bit sad,
  79. // there are a lot of various packages, with various APIs, some of them
  80. // are unmaintained. Fortunately this is something that will be fixed by
  81. // meteor-core at some point:
  82. //
  83. // https://trello.com/c/BGvIwkEa/48-easy-joins-in-subscriptions
  84. //
  85. // And in the meantime our code below works pretty well -- it's not even a
  86. // hack!
  87. this.cursor(Cards.find({ boardId }), function(cardId) {
  88. this.cursor(CardComments.find({ cardId }));
  89. this.cursor(Attachments.find({ cardId }));
  90. });
  91. // Board members. This publication also includes former board members that
  92. // aren't members anymore but may have some activities attached to them in
  93. // the history.
  94. //
  95. this.cursor(Users.find({
  96. _id: { $in: _.pluck(board.members, 'userId') },
  97. }), function(userId) {
  98. // Presence indicators
  99. this.cursor(presences.find({ userId }));
  100. });
  101. });
  102. return this.ready();
  103. });