feat: Backward compatibility for settings API #2448
Merged
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.
This PR adds the backward compatbility support in PyFluent settings API using the
child-aliases
/command-aliases
/query-aliases
attributes in settings API.A tree of alias-objects mimicking the original object tree is constructed on-access basis during runtime. For an object hierarchy
A -> B -> C
, IfA1
is an alias ofA
,A1.B
andA1.C
are also aliases and the backward compatibility message for set_state is shown at all levels. The_Alias
base class prints the backward compatibility message on various journaling points using the scheme_eval function which is passed through theget_root()
function.Please see the Fluent side PR for more details on flobject.py change.
I'm also incorporating changes from #2428 which simplifies some code requiring access to original settings object classes.