Fixed bug where SectionProperty objects did not have sequential ids when using multiple push components, leading to errors when trying to read them in to a Dictionary.
@peterjamesnugent to confirm, the following actions are now queued:
- check `code-compliance`
- check `documentation-compliance`
- check `project-compliance`
- check `core`
- check `null-handling`
- check `serialisation`
- check `versioning`
- check `installer`
- check `copyright-compliance`
There are 5 requests in the queue ahead of you.
@peterjamesnugent to confirm, the following actions are now queued:
- check `installer`
- check `versioning`
There are 2 requests in the queue ahead of you.
Issues addressed by this PR
Closes #359
Test files
https://burohappold.sharepoint.com/:u:/r/sites/BHoM/02_Current/12_Scripts/01_Issue/BHoM/MidasCivil_Toolkit/%23359-SectionPropertyIdBug.gh?csf=1&web=1&e=iWCRtf
Changelog
SectionProperty
objects did not have sequential ids when using multiple push components, leading to errors when trying to read them in to aDictionary
.Additional comments