shows quests on ajax instead of right away

[owocki]

Description

shows quests on ajax instead of right away

this is for sleep reasons..loading the quests is the most performance intensive part of the quests LP load

Refers/Fixes

#5436

Testing

tested locally

[codecov]

Codecov Report

Merging #5444 into master will increase coverage by 0.3%.
The diff coverage is 2.17%.

@@            Coverage Diff            @@
##           master    #5444     +/-   ##
=========================================
+ Coverage   29.67%   29.97%   +0.3%     
=========================================
  Files         242      242             
  Lines       20601    20724    +123     
  Branches     2968     3031     +63     
=========================================
+ Hits         6114     6213     +99     
- Misses      14236    14259     +23     
- Partials      251      252      +1

Impacted Files	Coverage Δ
app/app/urls.py	90% <ø> (ø)	⬆️
app/quests/views.py	15.04% <0%> (-0.85%)	⬇️
app/kudos/views.py	22.1% <100%> (ø)	⬆️
app/dashboard/views.py	12.94% <0%> (ø)	⬆️
...rketing/management/commands/no_applicants_email.py	0% <0%> (ø)	⬆️
...eting/management/commands/assemble_leaderboards.py	79.17% <0%> (+4.07%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0050d1c...6e3e11a. Read the comment docs.

[danlipert]

Looks good - just one issue that may cause problems for folks developing on their local

[octavioamu]

being with ajax shouldn't the logic of the loading be on the Js code? Also Seems if there is a fetching error or not results the loading is being forever. Or I'm missing something?

[owocki]

being with ajax shouldn't the logic of the loading be on the Js code?

it is?

i havent encountered a situation in which there is a fetching error.. is there one you think we should be handling?