Adds new options for moving precedences and maintaining the positioning between dependent tasks #535
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In an application for this gantt chart, I need the dependent tasks to be linked. As such, a change to one triggers a change in others.
Consider the following example where Task B "Write new content" depends on Task A "Redesign website".

If Task A is moved, or the ending time is changed, then that should result in Task B moving by the same amount.


Also, the precedent tasks are important. If Task B was moved or the start time was changed, the Task A should ,pve by the same amount.


To this end, this PR introduces two new parameters:
move_precedences
andmaintain_dependency_position
.move_precedence
is set totrue
, then the precedent tasks are moved in the same way that the dependent tasks were moved previously.maintain_dependency_position
parameter ensures that any change to tasks results in a move in the dependent tasks.true
, the changes in the dependent task start time will cause a movement in the preceding task.