Remove support for Omicron txt output #170
Open
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
Collaborator
|
Have we conirmed that people are not using this option. As long as Omicron supports the format I would like to kee it. |
duncanmmacleod
added
the
pr:backwards-incompatible
Member
Author
|
@areeda, I would that anyone using it should be forced to stop. Storing triggers as ASCII is inefficient in many ways compared to the other binary options. If you agree with that, then the easiest way to stop them is to pull the support out from underneath, even if it is a little callous. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 closes #169 by removing support for configuring Omicron to produce, or postprocessing
.txtoutput files.