Properties from Schedule, parameter on Project Info

When utilizing properties from Schedules, should it be expected the property set should reflect the displayed schedule?

I've been approached by a project to help with achieving this.

One aspect I've noticed is that the schedule can contain parameter extracted from the project info.
But in the ifc export code, this is ignored by this filter.

ScheduleFieldType fieldType = field.FieldType;
if (fieldType != ScheduleFieldType.Instance && fieldType != ScheduleFieldType.ElementType)
continue;

I can make a pull request where this persists if the fieldType is project info, but I'm not sure whether this break of legacy behavior will upset other users. Perhaps an option needs to be provided for legacy behaviour?

Thanks,

Jon

Start with the IFC export filter shown in the issue and trace how ScheduleFieldType values are handled, especially project-info parameters. Determine the intended behavior for displayed schedule properties and whether legacy behavior must remain configurable; done requires an agreed behavior and validation that schedule exports follow it.

Written by the indexing model from the issue text.