-
Notifications
You must be signed in to change notification settings - Fork 32
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
New economic baseline section. #61
Comments
So, there would be two radio button sections? One with the title "Deviation from CBO..." and then some choices, and then another with the title "Replacement for... " and then choices. Is that correct? Is the initial state of each radio button "unselected" for both? What should happen if a selection is made in both radio button areas? |
Yes.
The initial selection should be "Deviation from CBO" and the default value will be 0, so there will be no deviation from CBO. If someone clicks the other radio button, it should automatically unselect the Deviation from CBO radio button and vice versa. |
OK, got it. SOS @mistakevin is the above a quick surgical strike for you? |
(just to clarify, the displayed names of the parameters and all other meta data should com from the attributes in current_law_policy.json as with the other fields on the input page. ) |
@MattHJensen I think everything is clear here now except for how to populate the radio button choices. |
Actually I think we're not on the same page w the radio buttons. I anticipate just two selections: one choice is _factor_target and one choice is _factor_adjustment. The user uses text boxes to enter values, just like other params. |
That's right. And the 'information i' pulling in the description attribute. |
Resolved and closing. |
There should be a new section on the TaxBrain input page that gives the users access to the economic growth rate work that @Amy-Xu is conducting in #383 (previously #368). I'm hoping that @PeterDSteinberg or @talumbau take this one.
This feature is a bit different than others because the growth update should be applied to both the plan x and plan y calculators. Also, only one of these parameters should be changed at a time. Susan suggested a radio button, which is what I display in the sketch above.
Note that I suspect #383 will need some refactoring, which @Amy-Xu is taking care of today, before it will work seemlessly with dropq. See this comment: PSLmodels/Tax-Calculator#368 (comment).
The text was updated successfully, but these errors were encountered: