Skip to content
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

Replace if_18f_employee field with property #1078

Merged
merged 5 commits into from
May 5, 2020
Merged

Conversation

Jkrzy
Copy link
Contributor

@Jkrzy Jkrzy commented May 5, 2020

Description

For #1034, dropping is_18f_employee from UserData model.

As we move towards Organization being a required field, we drop this independent field and replace with a property whose value is derived from Organization.

We'll no longer have to maintain a separate field in addition to Organization in order to serve data re: a user being in 18F or not.

Jkrzy added 3 commits May 4, 2020 22:16
As we move towards Organization being a required field,
we drop this indepdent field and replace with a property
whose value is derived from Organization.
Copy link
Member

@mgwalker mgwalker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh noice

tock/employees/tests/test_models.py Show resolved Hide resolved
Jkrzy added 2 commits May 5, 2020 09:14
Updating so we always return True or False
and clarifying test case a bit.
Description of billable_expectation belongs
in help_text, not as the verbose field name.

Also adding another filter to the UserData admin
to assist survey/inspection.
@Jkrzy Jkrzy merged commit 1bc24ce into master May 5, 2020
@Jkrzy Jkrzy deleted the 18f-employee-property branch May 29, 2020 15:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants