Skip to content

Conversation

@adv12
Copy link
Contributor

@adv12 adv12 commented Jan 21, 2026

This PR consolidates GetOperationTypeFromProductCategory and OverrideOperationTypeFromWorkingDatas into a single method, GetOperationType. This allows future mixing of product type and device operation type logic to achieve the best possible guess at operation type.

It also mostly restores a bit of functionality I removed in #256. Prior to that PR, Variety crops always resulted in a SowingAndPlanting operation type. Since that PR, Variety crops have fallen through to later logic. I restored the Variety logic with an exception for when the device operation type is Harvest (the reason for #256).

{
case CategoryEnum.Variety:
// It's technically an error to log Harvesting as a variety product,
// but this was observed by Ag Leader in a CNH Pro1200 file in August 2025
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The issue is due to Mappers/Manufacturers/CNH.cs @ 290. It is more of framework limitation than an error since Category lacks an enumeration item for Harvested Commodity. Arguably the "right" fix would be for us to add that to the framework and then make these changes, but the conditional you have here will probably cover us in all cases. The other possibility is to determine the harvested product by using reflection on the type. I'm fine with this going out like this for now, however.

@strhea
Copy link
Contributor

strhea commented Jan 23, 2026

No objection from me. @kelly-nelson Does this need Doug to weigh in?

@kelly-nelson
Copy link
Contributor

@dwalgren

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants