-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sanitise Data leaving Travis #20
Comments
@matt-oc Can you run them through a pretty printer and use the code formatting, otherwise I can't read them |
I like ID, Group, Last State and Time, they are valuable and seem to be consistent and likely to have correct information (the language for instance is usually incorrect on Travis) |
@mcdonnelldean I'm trying to find one to give a nice output, bear with me! |
Also, A link to the latest build |
Yes thats a good point so we have ID, Group, Last State and time, and a URL link to the Travis page. That output looks a bit better now too 👍 |
Can you make a fake payload at the bottom of your original message, with the ones you think are right, I can edit accordingly then. |
As a JSON object |
Initial proposed object now implemented |
@matt-oc Lets leave this and the others open for the time being, just in case we want more from them |
@mcdonnelldean Yep will do, I'm updating the original comment whenever the data is changed so people know where we are with regards to data. |
The data leaving the Travis module (and npm and github) needs to be decided upon before it leaves. The problem is we have alot of data for each module and the data for each query may be different. Below are three example dumps from the Travis module:
Searching for Fuge:
Lodash:
Nodezoo:
Proposed object:
The text was updated successfully, but these errors were encountered: