Comments (1)
- Default to main branch, rather than assuming it's "main"
- Fail gracefully when branch doesn't exist, offer 2 closest matches
- Fail gracefully when object doesn't exist in any commit
from
andto
args ingit_history()
where they can be : dates, commits, tagsfrom
arg inreview_object_history()
- Cuter function names
- Arg
step = "commit"
, that we can also set to "tag", "parent commit", "day", "week", "month" "year", and we'll show the diff over the period. we can also use regex() to single out commits that have a given format or mention a given keyword - Meta data for changes, a "change" is a commit/object pair. We might have an impure commit, adding comments in one function and renaming another, but the "changes" in this case would be pure. Changes can be:
- doc changes
- argument changes
- style
- comments
- variable renaming
- ... ?
- other (whenever we can't detect a category)
- We could filter on this meta data but it's a little different from the
step
above because when filtering on metadata we want the diff to the direct previous commit, not the commit one "step" before, so I think this would be a separate function. - Can we detect renaming of functions ? we can be strict about it (only name changes) or lax (object 1 disappeared, and object 2 appeared between the same objects in the same file, maybe with a degree of similarity in the code.
- Try to implement
review_object_history()
without a need from the data, computing on the go, and see if it's really too slow to be practical, since this would work only commit to commit, this is also a separate function - Provide multiple objects, to
review_object_history()
: some objects go together, maybe generic and methods for instance, we might want to see the changes to all of them, we'd go by step, then for a given step by object alphabetically - R cannot detect key presses unless run in a terminal, but shiny apps can, we can have a widget ans use 1 2 to go forward backward, and 3 to toggle different diff modes (full side by side, side by side with a 10 lines context, unified (standard git view))
- Filter by author ? so commits by auth1 auth1 auth2 auth2 auth2 auth1 become : auth1 auth1 OTHER auth1 (we "squash" the changes of other authors but still show them, this is for the stepwise function,
from blame.
Related Issues (4)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from blame.