The rules for how the PlanText needs to be structured can be found in eFormAPI/Plugins/TimePlanning.Pn/TimePlanning.Pn/Infrastructure/Helpers/GoogleSheetHelper.cs
Basically this new part of the code is going to do the reverse of the parsing of the PlanText and need to be able to generate the correct output.
Doing this would be a good time to refactor the GoogleSheetHelper.cs into a submethod that will do the parsing, so it's testable and usable for checking if the selected start/stop for a planning is generating the correct PlanText which in turn should result in bitwise the same start/stop as the input.
The rules for how the PlanText needs to be structured can be found in eFormAPI/Plugins/TimePlanning.Pn/TimePlanning.Pn/Infrastructure/Helpers/GoogleSheetHelper.cs
Basically this new part of the code is going to do the reverse of the parsing of the PlanText and need to be able to generate the correct output.
Doing this would be a good time to refactor the GoogleSheetHelper.cs into a submethod that will do the parsing, so it's testable and usable for checking if the selected start/stop for a planning is generating the correct PlanText which in turn should result in bitwise the same start/stop as the input.