Repository navigation
Conversation
Member
Author
|
Any thoughts on this approach from @Lnaden @andrrizzi @pgrinaway? |
Contributor
|
Nothing particularly smart. The only thing that comes to mind is to maintain a dictionary |
This branch has not been deployed
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
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.
Addresses #190
This PR begins to implement a system where we can add keyword tags to each system to enable autodiscovery of testsystems that have useful properties, like are quick to run on travis (or too slow to run on travis).
Instead of having the initializer define the tags, it would be useful to be able to query this without having to actually construct the object, since that construction itself can be slow. I'm still trying to think of how best to tackle that.