Skip to content

Conversation

BrianJKoopman
Copy link
Member

Description

This moves _enforce_field_name_rules() out of the Aggregator agent part of the ocs library and into the Feed class, where similar field related static methods are. This eliminates the dependency of spt3g/so3g on the Registry Agent.

Motivation and Context

Resolves #239

How Has This Been Tested?

The full test suite was run after the move. Also tested on a system without an spt3g/so3g installation (with -m 'not spt3g') to verify that Registry tests no longer depend on spt3g/so3g.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • Unless I am preparing a release, I have opened this PR onto the develop branch.

This was causing issues with the installation within the container, which
cropped up when testing other changes. We shouldn't need the flag within the
container anyway.
@BrianJKoopman BrianJKoopman merged commit 24c6a61 into develop Dec 21, 2021
@BrianJKoopman BrianJKoopman deleted the koopman/move-enforce-field-name-rules branch December 21, 2021 22:31
@BrianJKoopman BrianJKoopman mentioned this pull request Feb 2, 2022
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.

Move Provider._enforce_field_name_rules out of Provider
2 participants