Always assign new ids for objects being created

IsakNaslundBh commented 4 years ago

NOTE: Depends on

Issues addressed by this PR

Closes #208

Removing check if object already has an AdapterId for objects to be created. See issue for more details, but this means new objects, set to be created, should always get a new id assigned, independent if they had one before or not.

Test files

@kThorsager do you have a link to the scripts giving you problems?

Changelog

Removing check if AdapterNameId already exists in custom data before assigning fresh id to objects being created.

Additional comments

IsakNaslundBh commented 4 years ago

/azp run BHoM_Adapter.CheckInstaller

azure-pipelines[bot] commented 4 years ago

Azure Pipelines successfully started running 1 pipeline(s).

IsakNaslundBh commented 4 years ago

Thanks @kThorsager ! Will run some final tests myself, then merge if things are fine

BHoM / BHoM_Adapter