You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In ericduran#30 Eric talks about rewriting the app in Angular and just reading json data. I think the first step would be to export every parsed commit into a useful json structure.
I'm thinking the structure for each commit would be something like:
{
'message': string,
'author': string,
'users: {
'key': value
},
'time': time,
}
What else would be useful?
The text was updated successfully, but these errors were encountered:
They're commenting about making it in node instead of ruby as well, a json per commit will be a huge file/chunk of files, maybe is better to generate a contributors.json and a companies.json (potentially also a json per contributor and company if we want to have individual pages (#5) ?)
@pcambra It depends on what we want to do on those individual pages, I'm thinking line graphs of commits over time, which means we would need information of every commit. It doesn't feel great only generating the data that we need to achieve specific functionality, it makes it very inflexible in the future.
@ElijahLynn That's the problem with the current data.json, it's useless for anything other than the current index.html
In ericduran#30 Eric talks about rewriting the app in Angular and just reading json data. I think the first step would be to export every parsed commit into a useful json structure.
I'm thinking the structure for each commit would be something like:
{
'message': string,
'author': string,
'users: {
'key': value
},
'time': time,
}
What else would be useful?
The text was updated successfully, but these errors were encountered: