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

prune_current_assignments() should also clear considered_destinations #55

Open
dgets opened this issue Dec 29, 2018 · 0 comments
Open
Assignees
Labels
enhancement New feature or request maintainability

Comments

@dgets
Copy link
Owner

dgets commented Dec 29, 2018

If ShipHistory is to be fully integrated, it will be necessary to have prune_current_assignments() also go into glo.Variables.considered_destinations, and wipe out any destinations that the ship was previously considering. This would require either modification of considered_destinations from a list into a dict, in order to store things along with the ship.id, or else a considered destination field could be added to the ShipHistory class, enabling it to be tucked in along with everything else that belongs there (this is the way I'm going to try to handle it).

@dgets dgets added enhancement New feature or request maintainability labels Dec 29, 2018
@dgets dgets added this to the maintainability milestone Dec 29, 2018
@dgets dgets self-assigned this Dec 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request maintainability
Projects
None yet
Development

No branches or pull requests

1 participant