Revert changing config variables ($srfg to $wgSrfg) #848
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
|
I don't think the failing tests are a problem of this branch... |
|
@robinwiel - I have reverted all the config var in previous state before the mentioned commit, and tested it. So far looks good. It will be commited in 15 minutes. Just pull the latest changes from SRF and test it on your fork. |
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 reverts the remainder of config variables from Semantic Result Formats (starting with "srfg") that were refactored to start with "wgSrfg". These config variables do not exist, and therefore some functionality does not work anymore.
The previous reverts were done in this issue: #842
The refactoring was done in commit 5515deb.
@gesinn-it-ilm Could you have a look?