Mixing
Showing the list of pull_requests on the homepage
I have a model Pull_Requests in my database that's containing data and I want to display this data into an HTML table on my homepage. So I created the view, urls and home files as they are below but I'm getting nothing when I run the app. As I am new in this area, I'm not able to detect what could be the issue. Thanks in advance for your help.
from django.shortcuts import render
from django.views import View
class home(ListView):
template_name = 'home.html'
def get_queryset(self, request):
pull_requestsList = Pull_Requests.objects.all()
pullRequest_dict = {'pull_requests': pull_requestsList}
return render(request, self.template_name, pullRequest_dict)
from django.urls import path from. import views
urlpatterns = [
path('', views.home, name='home'),
]
% extends "base.html" %}
{% load static %}
{% block body %}
<div class="container">
{% if pullrequests %}
{% for field in pullrequests %}
<table>
<tr>
<th>{{ field.pr_project }}</th>
<th>{{ field.pr_id }} </th>
<th>{{ field.nd_comments }} </th>
<th>{{ field.nb_added_lines_code }}</th>
<th>{{ field.nb_deleted_lines_code }}</th>
<th>{{ field.nb_commits }}</th>
<th>{{ field.nb_changed_fies }}</th>
<th>{{ field.Closed_status }}</th>
<th>{{ field.reputation }}</th>
<th>{{ field.Label }}</th>
</tr>
</table>
{% endfor %}
{% else %}
<strong> There is no pull request in the database. </strong>
{% endif %}
</div>
{% endblock %}
django sqlite
asked Nov 22 '18 at 8:56
Abdillah MohamedAbdillah Mohamed
917
|
show 7 more comments
I have a model Pull_Requests in my database that's containing data and I want to display this data into an HTML table on my homepage. So I created the view, urls and home files as they are below but I'm getting nothing when I run the app. As I am new in this area, I'm not able to detect what could be the issue. Thanks in advance for your help.
from django.shortcuts import render
from django.views import View
class home(ListView):
template_name = 'home.html'
def get_queryset(self, request):
pull_requestsList = Pull_Requests.objects.all()
pullRequest_dict = {'pull_requests': pull_requestsList}
return render(request, self.template_name, pullRequest_dict)
from django.urls import path from. import views
urlpatterns = [
path('', views.home, name='home'),
]
% extends "base.html" %}
{% load static %}
{% block body %}
<div class="container">
{% if pullrequests %}
{% for field in pullrequests %}
<table>
<tr>
<th>{{ field.pr_project }}</th>
<th>{{ field.pr_id }} </th>
<th>{{ field.nd_comments }} </th>
<th>{{ field.nb_added_lines_code }}</th>
<th>{{ field.nb_deleted_lines_code }}</th>
<th>{{ field.nb_commits }}</th>
<th>{{ field.nb_changed_fies }}</th>
<th>{{ field.Closed_status }}</th>
<th>{{ field.reputation }}</th>
<th>{{ field.Label }}</th>
</tr>
</table>
{% endfor %}
{% else %}
<strong> There is no pull request in the database. </strong>
{% endif %}
</div>
{% endblock %}
django sqlite
asked Nov 22 '18 at 8:56
Abdillah MohamedAbdillah Mohamed
917
You've only shown part of the code. Where is the rest of the view class that get_queryset belongs to? And what are the patterns in urls.py?
– Daniel Roseman
Nov 22 '18 at 9:44
Don't post code as comments, it is unreadable. Edit the question and post your code there. And where is the URL that actually points to that view?
– Daniel Roseman
Nov 22 '18 at 10:11
@Daniel Roseman Sir, are you checking, please?
– Abdillah Mohamed
Nov 22 '18 at 11:13
I can't really understand this code, I'm afraid. Is the indentation right? Is Pull_RequestView really nested insidehome?
– Daniel Roseman
Nov 22 '18 at 11:48
I think is home. Or you can suggest something that can work because I really don't know how does it work. Everything turns around home but as I don't how it works that my code looks like a mess. Thanks
– Abdillah Mohamed
Nov 22 '18 at 12:08
|
show 7 more comments
I have a model Pull_Requests in my database that's containing data and I want to display this data into an HTML table on my homepage. So I created the view, urls and home files as they are below but I'm getting nothing when I run the app. As I am new in this area, I'm not able to detect what could be the issue. Thanks in advance for your help.
from django.shortcuts import render
from django.views import View
class home(ListView):
template_name = 'home.html'
def get_queryset(self, request):
pull_requestsList = Pull_Requests.objects.all()
pullRequest_dict = {'pull_requests': pull_requestsList}
return render(request, self.template_name, pullRequest_dict)
from django.urls import path from. import views
urlpatterns = [
path('', views.home, name='home'),
]
% extends "base.html" %}
{% load static %}
{% block body %}
<div class="container">
{% if pullrequests %}
{% for field in pullrequests %}
<table>
<tr>
<th>{{ field.pr_project }}</th>
<th>{{ field.pr_id }} </th>
<th>{{ field.nd_comments }} </th>
<th>{{ field.nb_added_lines_code }}</th>
<th>{{ field.nb_deleted_lines_code }}</th>
<th>{{ field.nb_commits }}</th>
<th>{{ field.nb_changed_fies }}</th>
<th>{{ field.Closed_status }}</th>
<th>{{ field.reputation }}</th>
<th>{{ field.Label }}</th>
</tr>
</table>
{% endfor %}
{% else %}
<strong> There is no pull request in the database. </strong>
{% endif %}
</div>
{% endblock %}
django sqlite
asked Nov 22 '18 at 8:56
Abdillah MohamedAbdillah Mohamed
917
I have a model Pull_Requests in my database that's containing data and I want to display this data into an HTML table on my homepage. So I created the view, urls and home files as they are below but I'm getting nothing when I run the app. As I am new in this area, I'm not able to detect what could be the issue. Thanks in advance for your help.
from django.shortcuts import render
from django.views import View
class home(ListView):
template_name = 'home.html'
def get_queryset(self, request):
pull_requestsList = Pull_Requests.objects.all()
pullRequest_dict = {'pull_requests': pull_requestsList}
return render(request, self.template_name, pullRequest_dict)
from django.urls import path from. import views
urlpatterns = [
path('', views.home, name='home'),
]
% extends "base.html" %}
{% load static %}
{% block body %}
<div class="container">
{% if pullrequests %}
{% for field in pullrequests %}
<table>
<tr>
<th>{{ field.pr_project }}</th>
<th>{{ field.pr_id }} </th>
<th>{{ field.nd_comments }} </th>
<th>{{ field.nb_added_lines_code }}</th>
<th>{{ field.nb_deleted_lines_code }}</th>
<th>{{ field.nb_commits }}</th>
<th>{{ field.nb_changed_fies }}</th>
<th>{{ field.Closed_status }}</th>
<th>{{ field.reputation }}</th>
<th>{{ field.Label }}</th>
</tr>
</table>
{% endfor %}
{% else %}
<strong> There is no pull request in the database. </strong>
{% endif %}
</div>
{% endblock %}
django sqlite
django sqlite
asked Nov 22 '18 at 8:56
Abdillah MohamedAbdillah Mohamed
917
asked Nov 22 '18 at 8:56
Abdillah MohamedAbdillah Mohamed
917
edited Nov 22 '18 at 16:54
Abdillah Mohamed
asked Nov 22 '18 at 8:56
Abdillah MohamedAbdillah Mohamed
917
asked Nov 22 '18 at 8:56
Abdillah MohamedAbdillah Mohamed
917
asked Nov 22 '18 at 8:56
Abdillah MohamedAbdillah Mohamed
917
917
You've only shown part of the code. Where is the rest of the view class that get_queryset belongs to? And what are the patterns in urls.py?
– Daniel Roseman
Nov 22 '18 at 9:44
Don't post code as comments, it is unreadable. Edit the question and post your code there. And where is the URL that actually points to that view?
– Daniel Roseman
Nov 22 '18 at 10:11
@Daniel Roseman Sir, are you checking, please?
– Abdillah Mohamed
Nov 22 '18 at 11:13
I can't really understand this code, I'm afraid. Is the indentation right? Is Pull_RequestView really nested insidehome?
– Daniel Roseman
Nov 22 '18 at 11:48
I think is home. Or you can suggest something that can work because I really don't know how does it work. Everything turns around home but as I don't how it works that my code looks like a mess. Thanks
– Abdillah Mohamed
Nov 22 '18 at 12:08
|
show 7 more comments
You've only shown part of the code. Where is the rest of the view class that get_queryset belongs to? And what are the patterns in urls.py?
– Daniel Roseman
Nov 22 '18 at 9:44
Don't post code as comments, it is unreadable. Edit the question and post your code there. And where is the URL that actually points to that view?
– Daniel Roseman
Nov 22 '18 at 10:11
@Daniel Roseman Sir, are you checking, please?
– Abdillah Mohamed
Nov 22 '18 at 11:13
I can't really understand this code, I'm afraid. Is the indentation right? Is Pull_RequestView really nested insidehome?
– Daniel Roseman
Nov 22 '18 at 11:48
I think is home. Or you can suggest something that can work because I really don't know how does it work. Everything turns around home but as I don't how it works that my code looks like a mess. Thanks
– Abdillah Mohamed
Nov 22 '18 at 12:08
You've only shown part of the code. Where is the rest of the view class that get_queryset belongs to? And what are the patterns in urls.py?
– Daniel Roseman
Nov 22 '18 at 9:44
You've only shown part of the code. Where is the rest of the view class that get_queryset belongs to? And what are the patterns in urls.py?
– Daniel Roseman
Nov 22 '18 at 9:44
Don't post code as comments, it is unreadable. Edit the question and post your code there. And where is the URL that actually points to that view?
– Daniel Roseman
Nov 22 '18 at 10:11
Don't post code as comments, it is unreadable. Edit the question and post your code there. And where is the URL that actually points to that view?
– Daniel Roseman
Nov 22 '18 at 10:11
@Daniel Roseman Sir, are you checking, please?
– Abdillah Mohamed
Nov 22 '18 at 11:13
@Daniel Roseman Sir, are you checking, please?
– Abdillah Mohamed
Nov 22 '18 at 11:13
I can't really understand this code, I'm afraid. Is the indentation right? Is Pull_RequestView really nested inside
home?– Daniel Roseman
Nov 22 '18 at 11:48
I can't really understand this code, I'm afraid. Is the indentation right? Is Pull_RequestView really nested inside
home?– Daniel Roseman
Nov 22 '18 at 11:48
I think is home. Or you can suggest something that can work because I really don't know how does it work. Everything turns around home but as I don't how it works that my code looks like a mess. Thanks
– Abdillah Mohamed
Nov 22 '18 at 12:08
I think is home. Or you can suggest something that can work because I really don't know how does it work. Everything turns around home but as I don't how it works that my code looks like a mess. Thanks
– Abdillah Mohamed
Nov 22 '18 at 12:08
|
show 7 more comments
1 Answer
1
active
oldest
votes
You have multiple issues.
The main problem is that get_queryset is supposed to return a queryset, not render a template. Because you do not return a queryset, and don't set the model attribute on the view, Django has no way of knowing what type of objects you're intending to list and therefore doesn't create a pullrequests object in the template context.
That method isn't doing anything useful anyway; you should probably just remove it, and define the attribute instead. So your view is literally just:
class home(ListView):
template_name = 'home.html'
model = Pull_Requests
But note also that the name Django creates will be pull_requests_list, so you should use that in your template. (Also also, you don't need the if block; the for loop has an empty clause.) So:
{% block body %}
<div class="container">
{% for field in pull_requests_list %}
<table>
<tr>
<th>{{ field.pr_project }}</th>
<th>{{ field.pr_id }} </th>
<th>{{ field.nd_comments }} </th>
<th>{{ field.nb_added_lines_code }}</th>
<th>{{ field.nb_deleted_lines_code }}</th>
<th>{{ field.nb_commits }}</th>
<th>{{ field.nb_changed_fies }}</th>
<th>{{ field.Closed_status }}</th>
<th>{{ field.reputation }}</th>
<th>{{ field.Label }}</th>
</tr>
</table>
{% empty %}
<strong> There is no pull request in the database. </strong>
{% endfor %}
</div>
{% endblock %}
answered Nov 22 '18 at 17:23
Daniel RosemanDaniel Roseman
453k41584641
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53427110%2fshowing-the-list-of-pull-requests-on-the-homepage%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You have multiple issues.
The main problem is that get_queryset is supposed to return a queryset, not render a template. Because you do not return a queryset, and don't set the model attribute on the view, Django has no way of knowing what type of objects you're intending to list and therefore doesn't create a pullrequests object in the template context.
That method isn't doing anything useful anyway; you should probably just remove it, and define the attribute instead. So your view is literally just:
class home(ListView):
template_name = 'home.html'
model = Pull_Requests
But note also that the name Django creates will be pull_requests_list, so you should use that in your template. (Also also, you don't need the if block; the for loop has an empty clause.) So:
{% block body %}
<div class="container">
{% for field in pull_requests_list %}
<table>
<tr>
<th>{{ field.pr_project }}</th>
<th>{{ field.pr_id }} </th>
<th>{{ field.nd_comments }} </th>
<th>{{ field.nb_added_lines_code }}</th>
<th>{{ field.nb_deleted_lines_code }}</th>
<th>{{ field.nb_commits }}</th>
<th>{{ field.nb_changed_fies }}</th>
<th>{{ field.Closed_status }}</th>
<th>{{ field.reputation }}</th>
<th>{{ field.Label }}</th>
</tr>
</table>
{% empty %}
<strong> There is no pull request in the database. </strong>
{% endfor %}
</div>
{% endblock %}
answered Nov 22 '18 at 17:23
Daniel RosemanDaniel Roseman
453k41584641
add a comment |
You have multiple issues.
The main problem is that get_queryset is supposed to return a queryset, not render a template. Because you do not return a queryset, and don't set the model attribute on the view, Django has no way of knowing what type of objects you're intending to list and therefore doesn't create a pullrequests object in the template context.
That method isn't doing anything useful anyway; you should probably just remove it, and define the attribute instead. So your view is literally just:
class home(ListView):
template_name = 'home.html'
model = Pull_Requests
But note also that the name Django creates will be pull_requests_list, so you should use that in your template. (Also also, you don't need the if block; the for loop has an empty clause.) So:
{% block body %}
<div class="container">
{% for field in pull_requests_list %}
<table>
<tr>
<th>{{ field.pr_project }}</th>
<th>{{ field.pr_id }} </th>
<th>{{ field.nd_comments }} </th>
<th>{{ field.nb_added_lines_code }}</th>
<th>{{ field.nb_deleted_lines_code }}</th>
<th>{{ field.nb_commits }}</th>
<th>{{ field.nb_changed_fies }}</th>
<th>{{ field.Closed_status }}</th>
<th>{{ field.reputation }}</th>
<th>{{ field.Label }}</th>
</tr>
</table>
{% empty %}
<strong> There is no pull request in the database. </strong>
{% endfor %}
</div>
{% endblock %}
answered Nov 22 '18 at 17:23
Daniel RosemanDaniel Roseman
453k41584641
add a comment |
You have multiple issues.
The main problem is that get_queryset is supposed to return a queryset, not render a template. Because you do not return a queryset, and don't set the model attribute on the view, Django has no way of knowing what type of objects you're intending to list and therefore doesn't create a pullrequests object in the template context.
That method isn't doing anything useful anyway; you should probably just remove it, and define the attribute instead. So your view is literally just:
class home(ListView):
template_name = 'home.html'
model = Pull_Requests
But note also that the name Django creates will be pull_requests_list, so you should use that in your template. (Also also, you don't need the if block; the for loop has an empty clause.) So:
{% block body %}
<div class="container">
{% for field in pull_requests_list %}
<table>
<tr>
<th>{{ field.pr_project }}</th>
<th>{{ field.pr_id }} </th>
<th>{{ field.nd_comments }} </th>
<th>{{ field.nb_added_lines_code }}</th>
<th>{{ field.nb_deleted_lines_code }}</th>
<th>{{ field.nb_commits }}</th>
<th>{{ field.nb_changed_fies }}</th>
<th>{{ field.Closed_status }}</th>
<th>{{ field.reputation }}</th>
<th>{{ field.Label }}</th>
</tr>
</table>
{% empty %}
<strong> There is no pull request in the database. </strong>
{% endfor %}
</div>
{% endblock %}
answered Nov 22 '18 at 17:23
Daniel RosemanDaniel Roseman
453k41584641
You have multiple issues.
The main problem is that get_queryset is supposed to return a queryset, not render a template. Because you do not return a queryset, and don't set the model attribute on the view, Django has no way of knowing what type of objects you're intending to list and therefore doesn't create a pullrequests object in the template context.
That method isn't doing anything useful anyway; you should probably just remove it, and define the attribute instead. So your view is literally just:
class home(ListView):
template_name = 'home.html'
model = Pull_Requests
But note also that the name Django creates will be pull_requests_list, so you should use that in your template. (Also also, you don't need the if block; the for loop has an empty clause.) So:
{% block body %}
<div class="container">
{% for field in pull_requests_list %}
<table>
<tr>
<th>{{ field.pr_project }}</th>
<th>{{ field.pr_id }} </th>
<th>{{ field.nd_comments }} </th>
<th>{{ field.nb_added_lines_code }}</th>
<th>{{ field.nb_deleted_lines_code }}</th>
<th>{{ field.nb_commits }}</th>
<th>{{ field.nb_changed_fies }}</th>
<th>{{ field.Closed_status }}</th>
<th>{{ field.reputation }}</th>
<th>{{ field.Label }}</th>
</tr>
</table>
{% empty %}
<strong> There is no pull request in the database. </strong>
{% endfor %}
</div>
{% endblock %}
answered Nov 22 '18 at 17:23
Daniel RosemanDaniel Roseman
453k41584641
answered Nov 22 '18 at 17:23
Daniel RosemanDaniel Roseman
453k41584641
answered Nov 22 '18 at 17:23
Daniel RosemanDaniel Roseman
453k41584641
answered Nov 22 '18 at 17:23
Daniel RosemanDaniel Roseman
453k41584641
453k41584641
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53427110%2fshowing-the-list-of-pull-requests-on-the-homepage%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
You've only shown part of the code. Where is the rest of the view class that get_queryset belongs to? And what are the patterns in urls.py?
– Daniel Roseman
Nov 22 '18 at 9:44
Don't post code as comments, it is unreadable. Edit the question and post your code there. And where is the URL that actually points to that view?
– Daniel Roseman
Nov 22 '18 at 10:11
@Daniel Roseman Sir, are you checking, please?
– Abdillah Mohamed
Nov 22 '18 at 11:13
I can't really understand this code, I'm afraid. Is the indentation right? Is Pull_RequestView really nested inside
home?– Daniel Roseman
Nov 22 '18 at 11:48
I think is home. Or you can suggest something that can work because I really don't know how does it work. Everything turns around home but as I don't how it works that my code looks like a mess. Thanks
– Abdillah Mohamed
Nov 22 '18 at 12:08