-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Completed Issue #573 To Mark a job post as filled #595
base: main
Are you sure you want to change the base?
Completed Issue #573 To Mark a job post as filled #595
Conversation
@@ -2,6 +2,7 @@ | |||
# Django settings for account project |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please revert the settings.py file.
@@ -1,7 +1,24 @@ | |||
{% extends "shiny/slim.html" %} | |||
{% block page_header %}{{ flatpage.title | upper }}{% endblock %} | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please remove all the changes related to the flatpages and move them to a different PR as discussed.
I like the changes related to the job post model and the related migration. I didn't look into it, but how will django handle the old job posting in that don't have a filled status or filled date? Will users be able to edit their job filed status / date. Is that available in the user facing edit form and not just the admin. Most users will not have access to the admin. Please remove the ability to see a list of filled jobs as the AC was optional. I think it's fine to do, but we should have a separate template and view for that. Let's skip for now so we can close this PR. Please revert all other changes as noted. |
Re: django and old posts...
Can we add logic in the migrations to set a status for the old records?
…On Thu, Mar 13, 2025, 19:55 elmquist.dev ***@***.***> wrote:
I like the changes related to the job post model and the related migration.
I didn't look into it, but how will django handle the old job posting in
that don't have a filled status or filled date?
Will users be able to edit their job filed status / date. Is that
available in the user facing edit form and not just the admin. Most users
will not have access to the admin.
Please remove the ability to see a list of filled jobs as the AC was
optional. I think it's fine to do, but we should have a separate template
and view for that. Let's skip for now so we can close this PR.
Please revert all other changes as noted.
—
Reply to this email directly, view it on GitHub
<#595 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABHKYUBQVLFPXIRYWN4ZYE32UISGPAVCNFSM6AAAAABYPLBBQWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMRTGA2DEMZQGU>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
[image: elmq0022]*elmq0022* left a comment (chicagopython/chipy.org#595)
<#595 (comment)>
I like the changes related to the job post model and the related migration.
I didn't look into it, but how will django handle the old job posting in
that don't have a filled status or filled date?
Will users be able to edit their job filed status / date. Is that
available in the user facing edit form and not just the admin. Most users
will not have access to the admin.
Please remove the ability to see a list of filled jobs as the AC was
optional. I think it's fine to do, but we should have a separate template
and view for that. Let's skip for now so we can close this PR.
Please revert all other changes as noted.
—
Reply to this email directly, view it on GitHub
<#595 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABHKYUBQVLFPXIRYWN4ZYE32UISGPAVCNFSM6AAAAABYPLBBQWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMRTGA2DEMZQGU>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
No description provided.