-
Notifications
You must be signed in to change notification settings - Fork 30
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
Commits request #76
Comments
Honestly, we're not losing anything by having them inherit from Yeah, Not sure about the list of repositories, can you paste that here as well? |
I don't have this JSON fragment as all of my Bots are configured to have only one repository but from the naming you can guess that {
"commits": {
"715A78DA7313BF688CEE0585F44D4F0B2EAEE4B8": {
"XCSCommitCommitChangeFilePaths": [
{
"status": 4,
"filePath": "cells/NewProductCell.m"
},
{
"status": 4,
"filePath": "GreetingTextViewController.m"
},
{
"status": 4,
"filePath": "ViewControllers/NewChooseProductViewController.m"
}
],
"XCSCommitMessage": "Fixed ios7 bug",
"XCSBlueprintRepositoryID": "715A78DA7313BF688CEE0585F44D4F0B2EAEE4B8",
"XCSCommitContributor": {
"XCSContributorEmails": [
"[email protected]"
],
"XCSContributorName": "Foo Bar",
"XCSContributorDisplayName": "Foo Bar"
},
"XCSCommitHash": "aeb85aed37e633b6c9776cb863a39f922cb464d9",
"XCSCommitTimestamp": "2015-07-07T14:14:29.000Z",
"XCSCommitTimestampDate": [2015, 7, 7, 14, 14, 29]
}
}
} So, |
Hmm I doubt that. As you can see in |
👍 In that case |
Hmm only now I noticed that commits are a dictionary, not an array. Could you please post the whole output, both parts above in one JSON? Thanks |
I'll do it later and I'll try to prove many repositories scenario, so it'll turn into array of dictionaries. Give me time, I need some 🍖🍗🍲 |
I've checked multi-repository thing and it looks like you're right @czechboy0 - there will be only one repo and this view proves it: Regarding whole repository response JSON, here you go: {
"count": 1,
"results": [{
"_id": "272167d4affaf38ea93c6e403d001c60",
"_rev": "3-d856e17d2e88237b37c190591ddaaa48",
"commits": {
"A36AEFA3F9FF1F738E92F0C497C14977DCE02B97": [{
"XCSCommitCommitChangeFilePaths": [{
"status": 4,
"filePath": "Podfile.lock"
}],
"XCSCommitMessage": "new pods\n",
"XCSBlueprintRepositoryID": "A36AEFA3F9FF1F738E92F0C497C14977DCE02B97",
"XCSCommitContributor": {
"XCSContributorEmails": ["[email protected]"],
"XCSContributorName": "Honza Dvorsky",
"XCSContributorDisplayName": "Honza Dvorsky"
},
"XCSCommitHash": "deeca3728ed42406ee34e595feff4ed3bb78efb4",
"XCSCommitTimestamp": "2015-07-20T13:36:04.000Z",
"XCSCommitTimestampDate": [2015, 7, 20, 13, 36, 4, 0]
}, {
"XCSCommitCommitChangeFilePaths": [{
"status": 4,
"filePath": "README.md"
}],
"XCSCommitMessage": "more emoji",
"XCSBlueprintRepositoryID": "A36AEFA3F9FF1F738E92F0C497C14977DCE02B97",
"XCSCommitContributor": {
"XCSContributorEmails": ["[email protected]"],
"XCSContributorName": "Honza Dvorsky",
"XCSContributorDisplayName": "Honza Dvorsky"
},
"XCSCommitHash": "9f54f31ceffc89ddf735be250e911238631494aa",
"XCSCommitTimestamp": "2015-07-19T10:23:10.000Z",
"XCSCommitTimestampDate": [2015, 7, 19, 10, 23, 10, 0]
}, {
"XCSCommitCommitChangeFilePaths": [{
"status": 4,
"filePath": "CHANGELOG.md"
}],
"XCSCommitMessage": "changelog\n",
"XCSBlueprintRepositoryID": "A36AEFA3F9FF1F738E92F0C497C14977DCE02B97",
"XCSCommitContributor": {
"XCSContributorEmails": ["[email protected]"],
"XCSContributorName": "Honza Dvorsky",
"XCSContributorDisplayName": "Honza Dvorsky"
},
"XCSCommitHash": "98438eee1e8d891b34c777b57485f1ac251e5b1b",
"XCSCommitTimestamp": "2015-07-18T18:12:02.000Z",
"XCSCommitTimestampDate": [2015, 7, 18, 18, 12, 2, 0]
}, {
"XCSCommitCommitChangeFilePaths": [],
"XCSCommitMessage": "Merge pull request #72 from czechboy0/hd/cocoapods\n\nSwitching to CocoaPods",
"XCSBlueprintRepositoryID": "A36AEFA3F9FF1F738E92F0C497C14977DCE02B97",
"XCSCommitContributor": {
"XCSContributorEmails": ["[email protected]"],
"XCSContributorName": "Honza Dvorsky",
"XCSContributorDisplayName": "Honza Dvorsky"
},
"XCSCommitHash": "43653e7e9dcefab8089c05641d4a013002df9ff6",
"XCSCommitTimestamp": "2015-07-18T14:11:19.000Z",
"XCSCommitTimestampDate": [2015, 7, 18, 14, 11, 19, 0]
}, {
"XCSCommitCommitChangeFilePaths": [{
"status": 4,
"filePath": "XcodeServerSDK.podspec"
}],
"XCSCommitMessage": "new proper version\n",
"XCSBlueprintRepositoryID": "A36AEFA3F9FF1F738E92F0C497C14977DCE02B97",
"XCSCommitContributor": {
"XCSContributorEmails": ["[email protected]"],
"XCSContributorName": "Honza Dvorsky",
"XCSContributorDisplayName": "Honza Dvorsky"
},
"XCSCommitHash": "64526cb1dbe14b954c6edb080a9ae483b7fdfa2b",
"XCSCommitTimestamp": "2015-07-18T14:10:16.000Z",
"XCSCommitTimestampDate": [2015, 7, 18, 14, 10, 16, 0]
}]
},
"integration": "272167d4affaf38ea93c6e403d000d3a",
"botID": "272167d4affaf38ea93c6e403d0004c3",
"botTinyID": "F977308",
"endedTimeDate": [2015, 7, 20, 19, 36, 50, 237],
"doc_type": "commit",
"tinyID": "30C0AE6"
}]
} |
Hmm my guess is if you have git submodules, the |
|
Just the Bot's id. It's all about the |
Nevermind... Sometimes I just need to bite my tounge before a click comment... 😶 I'll sit on this tomorrow and will provide a proposal model for this. Thanks for your help! Much appreciated 👍 |
Anything else in this thread, @cojoj? Otherwise I'll close it. |
Sure, close it as for now we've move all of our conversation to #77 😉 |
I'm working on another point from #40 and I want to consult some matters before implementing anything.
It's obvious that List the commits included in an integration will consist of
Commit
model but... Response JSON is strange in some way and I'd like to clarify naming convention.Basically
integration/id/commits
response JSON looks like:IMHO, main object should be called something like
IntegrationCommits
because there'sCommits
array inside of it butCommit
, itself, doesn't containt fields to beXcodeServerEntity
.What's more,
commits
array contains an array of repositories which holds actual commits - so another model?Actual
Commit
looks like:I have a feeling I'm complicating everything but what do you think - should those models be separated or treated like one big, nested model and inherit from
XcodeServerEntity
?The text was updated successfully, but these errors were encountered: