q-table shows not data

[chyde90]

@PrasadChinwal So the QTable definitely has got the data, and there is no error in the console. Now, the only thing that could go wrong is that there is some kind of reactivity issue.
I have an idea: For testing purposes, please put the following in your response callback:

setTimeout(() => this.results = this.results.concat([]), 3000);

This is not a solution - but if you now (after 3 seconds) see the data, we have a clue where to search in order to actually fix the problem.

[PrasadChinwal]

@chyde90 I dont see the data in vue devtools for QTable. Do we have a clue on how to proceed? I really appreciate your help.

[chyde90]

@PrasadChinwal You don’t? But in the post before you said you do (and it’s in the screenshot). Or do you mean after you included the setTimeout thing? I’m confused

[PrasadChinwal]

@chyde90 My Bad. I do not see any data after adding the setTimeout();

[chyde90]

@PrasadChinwal uhhhm… really??^^
Just to make sure - you wrote it like this:

getReportByDate() {
	...
	axios.get( ... ).then((response) => {
		this.loading = false;
		this.results = (response.data);
		console.log(this.results);
		setTimeout(() => this.results = this.results.concat([]), 3000); // <--- this line added
	}).catch(error => {
		console.log(error);
	});
},

Right?
I expect either no changes at all, or that the table suddenly renders what you want to see.
Because this effectively does not do anyhing except triggering an update.

[PrasadChinwal]

@chyde90 Oh I see what you mean. I tried concatenating the response again in the timeout.

Unfortunately even with the above approach, as you mentioned there is no change at all. The data is present in devtools QTable but not displayed.

[PrasadChinwal]

@chyde90 Gist to File

[chyde90]

HAH! I think I found it!
You initialize pagination with page 2. Initialize it with 1 - does it work now?

[PrasadChinwal]

Oh dear lord ! Yes. I do see the data. I feel so stupid.
Anyways, Thanks a lot for helping out and I apologize for hogging your time.

[chyde90]

Yayyyy :DD Hey no problem… it was fun^^
No need to feel stupid there. It wasn’t really obvious because the pagination wasn’t visible.

Here is a tip / how I solve this kind of problem:
Remove everything from the code that is not needed to replicate the problem, feature by feature. And everytime test if you can reproduce the problem.
So when the problem doesn’t occur anymore, you know which part caused it. And if not, then you at least have a simpler and shorter version where you can spot it more easily

[PrasadChinwal]

@chyde90 That’s a really great advise. I really am thankful. I will try and use this trick whenever applicable. Have a great day ahead!