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

fix: ami chart values were not appearing after save and new #1952

Merged
merged 3 commits into from
Oct 12, 2021

Conversation

emilyjablonski
Copy link
Collaborator

@emilyjablonski emilyjablonski commented Oct 6, 2021

Pull Request Template

Issue

Addresses #1544

  • This change addresses the issue in full
  • This change addresses only certain aspects of the issue
  • This change is a dependency for another issue
  • This change has a dependency from another issue

Description

In LM if you created a unit by hitting "save and new" and then to the second unit tried to add an ami chart and percentage the values would not populate.

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Prototype/POC (not to merge)
  • This change is a refactor/address technical debt
  • This change requires a documentation update
  • This change requires a SQL Script

How Can This Be Tested/Reviewed?

Create a unit by hitting "save and new" and then to the second unit try to add an ami chart and percentage and ensure the fields populate.

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have reviewed the changes in a desktop view
  • I have reviewed the changes in a mobile view
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules
  • I have assigned reviewers
  • I have updated the changelog to include a description of my changes
  • I have run yarn generate:client if I made backend changes

@netlify
Copy link

netlify bot commented Oct 6, 2021

✔️ Deploy Preview for dev-storybook-bloom ready!

🔨 Explore the source changes: 9721f57

🔍 Inspect the deploy log: https://app.netlify.com/sites/dev-storybook-bloom/deploys/6165b2b4614f0d00072ffcb6

😎 Browse the preview: https://deploy-preview-1952--dev-storybook-bloom.netlify.app

@netlify
Copy link

netlify bot commented Oct 6, 2021

❌ Deploy Preview for dev-partners-bloom failed.

🔨 Explore the source changes: 9721f57

🔍 Inspect the deploy log: https://app.netlify.com/sites/dev-partners-bloom/deploys/6165b2b4d6449a00070e36c2

@netlify
Copy link

netlify bot commented Oct 6, 2021

❌ Deploy Preview for dev-bloom failed.

🔨 Explore the source changes: 9721f57

🔍 Inspect the deploy log: https://app.netlify.com/sites/dev-bloom/deploys/6165b2b4566349000793e446

Copy link
Collaborator

@seanmalbert seanmalbert left a comment

Choose a reason for hiding this comment

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

Looks good!

@seanmalbert seanmalbert merged commit cb65340 into dev Oct 12, 2021
seanmalbert added a commit to CityOfDetroit/bloom that referenced this pull request Jun 23, 2022
…using#1952)

* fix: ami chart values were not appearing after save and new

* docs: changelog

Co-authored-by: Sean Albert <smabert@gmail.com>
@emilyjablonski emilyjablonski deleted the 1544/qa-ami branch July 20, 2022 22:59
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.

None yet

2 participants