Repository navigation
Add custom message for 212s, 218s, and 219s #155
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
Changes from 2 commits
b27504f
c9aa792
a8e37b4
7e88648
c5ef4a5
16eb45d
6453a0f
57dea2e
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -194,6 +194,8 @@ def build_front_matter( | |
| Mapping of variable code for labels and tooltips | ||
| """ | ||
| special_multi = bool(df_target_pin["is_parcel_small_multicard"].iloc[0]) | ||
| analyst_review_classes = {"212", "218", "219"} | ||
| analyst_review = str(df_target_pin["char_class"].iloc[0]) in analyst_review_classes | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. [Suggestion, required] Preserving some discussion that we had over chat yesterday: It's not ideal that we're pulling this class from the first card in the PIN, given that cards can have different classes, and those classes don't necessarily match up with the PIN-level class. We're going to try switching to PIN-level class here, which will require updating the upstream view in |
||
|
|
||
| # Header | ||
| tp = df_target_pin.iloc[0] # all cards share the same PIN-level chars | ||
|
|
@@ -222,6 +224,8 @@ def build_front_matter( | |
| "cards": [], | ||
| "var_info": vars_dict, | ||
| "special_case_multi_card": special_multi, | ||
| "special_case_analyst_review": analyst_review, | ||
| "char_class": str(df_target_pin["char_class"].iloc[0]), | ||
| "environment": environment, | ||
| "is_prorated": tp["is_prorated"], | ||
| } | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.