Skip to content

RecordProcessor Warning on NULL FormIDs #6

@lojack5

Description

@lojack5

Brought up originally here: wrye-bash/wrye-bash#101

Essentially, it's possible for NULL FormIDs to get passed to various RecordProcessors if they exist in some of the sub-records. Sometimes, it's OK for there to be a NULL FormID there, sometimes it's not, but the current workings of the class don't allow for checking of the information, or even reporting which record had the NULL FormID in one of its sub-records.

The first bit can be solved with smarter passing of FormIDs to op.Accept, the second will require refactoring so RecordProcessor can have the information needed to display a better warning message.

As it is currently, most cases can be safely ignored, and it just leads to confusion.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions