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

Issue 356: Move NEBs out of Energy Opps. #359

Merged
merged 5 commits into from
Jan 21, 2025
Merged

Issue 356: Move NEBs out of Energy Opps. #359

merged 5 commits into from
Jan 21, 2025

Conversation

rmroot
Copy link
Collaborator

@rmroot rmroot commented Jan 17, 2025

connects #356

This moves the form for NEBs out of the Energy Opportunitites form.
Can link to energy opportunity using dropdown in NEB form now

This PR has all the changes from the re-designed sidebar. That one should be merged first and then I will update this one to clean up the number of file changes.

Copy link

Azure Static Web Apps: Your stage site is ready! Visit it here: https://gray-tree-06c66911e-359.westus2.4.azurestaticapps.net

Copy link

Azure Static Web Apps: Your stage site is ready! Visit it here: https://gray-tree-06c66911e-359.westus2.4.azurestaticapps.net

Copy link
Collaborator

@RLiNREL RLiNREL left a comment

Choose a reason for hiding this comment

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

Just a suggestion of tweaking the variable name from "EEM" to ""EEO" to align with energy efficiency opportunity.

Also, we discussed about acronym for the tab title/sidebar navs, @koay9f mentioned about switching all to acronyms (we have "NEBs" now, so change "energy efficiency opportunities" to "EEOs". I am fine with either, use acronyms or full names, as long as they are consistent everywhere.

@@ -10,5 +10,8 @@ export const LabelTooltips = {
},
"calculationMethod": {
"tooltip": "The method used to calculate impacts on the metric."
},
"associatedEEM": {
Copy link
Collaborator

Choose a reason for hiding this comment

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

should be "associatedEEO"?

<!-- <label class="col-sm-5 col-form-label" for="{{'associatedEEM'+nonEnergyBenefit.guid}}">Connected EEM</label> -->

<div class="col-sm-5 col-form-label">
<app-label-with-tooltip [field]="'associatedEEM'" [labelId]="'associatedEEM'+nonEnergyBenefit.guid"
Copy link
Collaborator

Choose a reason for hiding this comment

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

associatedEEM to associatedEEO?

@rmroot rmroot merged commit 14b3b00 into develop Jan 21, 2025
3 checks passed
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.

2 participants