Moving core functionality to core classes #4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
|
Need to first merge the other 2 PRs, so that tests wont be failing anymore, and then this |
senneberden
approved these changes
Nov 27, 2024
Collaborator
senneberden
left a comment
senneberden
left a comment
There was a problem hiding this comment.
OK! Just two methods moved to a superclass. However, it does seem that CAEnv has only one direct subclass, ActiveCAEnv, so I do wonder if we really need a separate CAEnv class. Is this done in order to accommodate potentially adding passive methods later?
Contributor
Author
|
Yes exactly, for creating a passive ca environment for passive methods |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some core functionality was in subclasses instead of the core classes. Need to move them there.