Skip to content

Conversation

lomky
Copy link
Member

@lomky lomky commented May 14, 2025

I rule and have completed some work on Case Manager that's ready for review!

(brief, plain english overview of your changes here)

This pull request makes the following changes:

  • fixes the Numeric check for configs
  • fixes the URL check for configs
  • updates other information for configs in comments

Testing:

  • Checked that every type of config validation is working properly in the GUI

For reviewer:

  • Adjust the title to explain what it does for the notification email to the listserv.
  • Tag this PR:
    • feature if it contains a feature, fix, or similar. This is anything that contains a user-facing fix in some way, such as frontend changes, alterations to backend behavior, or bug fixes.
    • dependencies if it contains library upgrades or similar. This is anything that upgrades any dependency, such as a Gemfile update or npm package upgrade.
  • If it contains neither, no need to tag this PR.

Copy link
Member

@colinxfleming colinxfleming left a comment

Choose a reason for hiding this comment

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

one thing to check but then go for it , thx kat

end

def validate_budget_bar_max
if !validate_number
Copy link
Member

Choose a reason for hiding this comment

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

When I put nah in here it lets me, though it seems to evaluate to zero -- I think this is because validate_number produces a string if something's up. That said it doesn't break anything on the frontend thankfully

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants