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.

Sign up for GitHub

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

Jump to bottom

Rename AllocationTarget to TargetLevel #1141

Merged
merged 1 commit into from
Feb 16, 2024
Merged

Rename AllocationTarget to TargetLevel #1141

merged 1 commit into from
Feb 16, 2024

Conversation

visr
Copy link
Member

@visr visr commented Feb 16, 2024

Follow up of #1082. We discussed we need to be clear it relates to a level, and this will be consistent with the to-be-created TargetFlow of #78.

@visr visr merged commit b392735 into main Feb 16, 2024
21 checks passed
@visr visr deleted the target_level branch February 16, 2024 16:06
Hofer-Julian pushed a commit that referenced this pull request Feb 22, 2024
@visr @Hofer-Julian
Rename AllocationTarget to TargetLevel (#1141)
e38d427 
Follow up of #1082. We discussed we need to be clear it relates to a
level, and this will be consistent with the to-be-created TargetFlow of
#78.
@visr visr mentioned this pull request Feb 22, 2024
Merged
Hofer-Julian pushed a commit that referenced this pull request Feb 23, 2024
@visr
Rename TargetLevel again: LevelDemand (#1172)
de2203f 
Follow up of #1082 and #1141.

As suggested by @gijsber, to go with FlowDemand of
#78, and renaming User to
UserDemand.

Not breaking since the TargetLevel node has not yet been in a release.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@visr