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

Freight: Rename CarrierControlerUtils ... #3513

Closed
kt86 opened this issue Oct 14, 2024 · 1 comment · Fixed by #3614
Closed

Freight: Rename CarrierControlerUtils ... #3513

kt86 opened this issue Oct 14, 2024 · 1 comment · Fixed by #3614
Assignees
Labels
maintenance things that should be done to improve code and UI

Comments

@kt86
Copy link
Contributor

kt86 commented Oct 14, 2024

...to CarrierControllerUtils (spelled with two "l"s).
This is a follow-up to #3511.
Otherwise, it is confusing to have it with one "l" in the freight contrib, and two "l" in core...

@kt86 kt86 added the maintenance things that should be done to improve code and UI label Oct 14, 2024
@kt86 kt86 self-assigned this Oct 14, 2024
@rewertvsp rewertvsp self-assigned this Nov 4, 2024
@kt86 kt86 moved this from Todo (high priority) to Todo (low priority) in MATSIM advanced weekly hackathon Nov 18, 2024
@kt86
Copy link
Contributor Author

kt86 commented Nov 25, 2024

Let's do matsim-vsp/logistics#314 first, so this is refactored automatically :)

@kt86 kt86 moved this from Todo (low priority) to In Progress in MATSIM advanced weekly hackathon Dec 1, 2024
@kt86 kt86 linked a pull request Dec 1, 2024 that will close this issue
@kt86 kt86 moved this from In Progress to To Be Reported in MATSIM advanced weekly hackathon Dec 2, 2024
@kt86 kt86 closed this as completed in #3614 Dec 2, 2024
@kainagel kainagel moved this from To Be Reported to Done in MATSIM advanced weekly hackathon Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance things that should be done to improve code and UI
Projects
Development

Successfully merging a pull request may close this issue.

2 participants