Allow Ramble to track the origin of a FOM #229
Merged
Conversation
This file contains 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
This change allows ramble to check if a FOM came from an app or a mod (and later perhaps that' its infact a dervied FOM) This is useful as it allow the user to tell if a fom came from an app or a mod during analysis, and can be decorate as such in text print
douglasjacobsen
approved these changes
Aug 1, 2023
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.
This change allows ramble to check if a FOM came from an app or a mod (and later perhaps that it is in fact a derived FOM)
This is useful as it allow the user to tell if a fom came from an app or a mod during analysis, and can be decorate as such in text print
This change also allows for the merging of contexts when a modifier and application emit the same context. Previously the applications context was lost.