Skip to content

Handle non-entity fields that are present in includes #626 - #627

Open
patrick-austin wants to merge 1 commit into
developfrom
bugfix/626-handle-type-includes
Open

Handle non-entity fields that are present in includes #626#627
patrick-austin wants to merge 1 commit into
developfrom
bugfix/626-handle-type-includes

Conversation

@patrick-austin

Copy link
Copy Markdown
Contributor

This PR will close #626

Description

As described on issue.

Testing Instructions

If the includes from the issue are used on an investigation query where Instrument.type is set, you should now see it returned (just like it would be without the mention of type).

I do have an automated test which would test this, coming in another PR soon (TM).

  • Review code
  • Check GitHub Actions build
  • If icatdb Generator Script Consistency Test CI job fails, is this because of a deliberate change made to the script to change generated data (which isn't actually a problem) or is here an underlying issue with the changes made?
  • Review changes to test coverage
  • Does this change mean a new patch, minor or major version should be made? If so, does one of the commit messages feature fix:, feat: or BREAKING CHANGE: so a release is automatically made via GitHub Actions upon merge?

Agile Board Tracking

Connect to #626

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.

Instrument.type not returned when type in list of includes

1 participant