Join the conversation

Wekan

General

Wekan is an open-source kanban board (Trello like) which allows a card-based task and to-do management.

More active conversations

Wekan / General

Cards.find() returns no cards

Wekan/General · December 26, 2020 at 11:28am

Cards.find() returns no cards

Wekan / General · December 26, 2020 at 11:28am (Edited 4 years ago)

Fooling around with putting together a simple My Cards implementation. However, I cannot get Cards.find() to return any cards. Boards.find() works perfectly.

cards() {
    // return [{ title: 'Card 1' }, { title: 'Card 2' }];
    const query = {
       archived: false,
       assignees: Meteor.userId(),
    };
    return Cards.find(query);
},

Is there something special that needs to be done to get Cards.find() to work?

P.S. Running the query in meteor mongo works perfectly.

Load previous messages

December 26, 2020 at 3:57pm

John Supplee@jrsupplee

3:57pm

Hmm. I need the cards from all boards not just a certain board. Is there no way to do it with Cards.find(). I see it used in other places.

December 26, 2020 at 8:14pm

Lauri Ojansivu@xet7

Team

8:14pm

That would be similar like searchCards, but without limiting it with boardId.

8:15pm

And it should show My Cards only from boards that user is member of

9:00pm

It seems that Cards.find() does search only from current board cards, that are loaded to webbrowser. To search from all cards of user etc, including cards that have not been loaded to webbrowser, I think you could search code with these keywords for related code: ./find.sh esSearch and ./find.sh EasySearch

9:03pm

Maybe with My Cards you are trying to do something similar like Public Boards https://github.com/wekan/wekan/pull/3008

December 27, 2020 at 2:59pm

John Supplee@jrsupplee

2:59pm

I guess I am being stupid, but I cannot understand why Cards.find() does not work. searchCards uses Cards.find() with boardId specified. The problem is not with my query as return Cards.find(); without a query (which should return all cards) returns an empty cursor.

I have a feeling that models/cards.js is not being imported properly.

December 27, 2020 at 4:47pm

Lauri Ojansivu@xet7

Team

4:47pm

Well, I don't know is it good idea to have both function cards() added and then use Cards.find(), those could get mixed

4:49pm

Anyway, point is to use code that searches serverside, like esSearch etc. Because not all data is loaded to browserside.

4:49pm

Meteor.js moves data automatically between clientside and serverside

4:49pm

If you have only opened one board, only that board cards are loaded to browserside. Not from any other board.

4:50pm

At browserside, there is minimongo, that is minimal version of MongoDB database, coded with Javascript

4:51pm

Meteor.js web framework listens changes from MongoDB, and updates immediately boards or all logged in users, in realtime

4:51pm

It's not anything about anybody being stupid.

4:52pm

It's just that things in Meteor.js do not work similarly like in other web frameworks

4:53pm

Meteor.js also automatically resolves write conficts of each user

4:54pm

Although, for some use cases, having manual control would in some cases improve things

5:12pm

Hmm, I don't know am I able to explain well enough.

5:26pm

Anyway, at https://github.com/wekan/wekan/pull/3008/files that code is very similar to what My Cards feature would be like. So, instead of adding Public, you would add My Cards. Then, you would copu that Public related code, so that instead of showing Public boards, you would show My Cards, creating new publication that sends to browserside all cards that are part of your My Cards, and no other data. Then, each of those cards would have link that points to that card full address in URL, the same you see in webbrowser URL bar currently when card is opened.

5:27pm

So I think, with so much already existing similar code and instructions, you should be able to add My Cards feature.

5:27pm

Oops typo above, copu that => copy that

5:28pm

publications/subscriptions do send cards to browserside

5:28pm

etc data

5:28pm

to browserside mongo, so they can be listed at webbrowser

5:29pm

Usually adding some new feature is like looking at some existing feature, and adding something similar.

5:31pm

It's not like it would require reading all of Wekan code. Instead, read and add only what is required, and try does it work.