« first day (296 days earlier)      last day (2884 days later) » 

00:00
RELOAD!
[retailcoder/Rubberduck] 6 commits. 5 opened issues. 3 closed issues. 1 issue comment.
2
[rolfl/MicroBench] 2 commits.
3
[Zomis/Prosit] 1 opened issue.
@Duga That's nice to see!
@RubberDuck Star it, then!
@Duga good point!
Wait.....
Sometimes I forget you're a bot.
lol
Sometimes I forget you're a duck.
That's enough for a day. Time to relax.
> Right now, if a merge succeeds, the Merge View simply closes.
Some feedback should be provided that the merge did indeed successfully complete.

Also, while taking care of this, remove the dependency on System.Forms.MessageBox in the presenter for reporting errors. Use the Merge View itself to report errors back. The presenter should have no references to the `System.Forms` namespace.
> sync Branch view's current branch with repo's current branch after merge
01:56
> Test setup for the error condition will look something like this.

var provider = new Mock<ISourceControlProvider>();
provider.Setup(git => git.Merge(It.IsAny<string>(), It.IsAny<string>()))
.Throws(new SourceControlException("message", new LibGit2Exception("inner message"));

//Assert State of Merge View
 
1 hour later…
02:57
I guess that's clearer:
            // bug: doesn't acquire named parameter usage
            var targets = _declarations.Items.Where(declaration =>
                IsSelectedDeclaration(selection, declaration) || IsSelectedReference(selection, declaration))
                .ToList();
        private bool IsSelectedReference(QualifiedSelection selection, Declaration declaration)
        {
            return declaration.References.Any(r => r.Selection.Contains(selection.Selection));
        }
...and yet I don't understand why it wouldn't acquire target on a named parameter usage, if a named parameter usage is indeed picked up as a reference of that parameter ...which I know it is, since renaming a parameter does rename named parameters...
well, first off ...there wouldn't be more than a single declaration or reference matching the selection, so that Where and ToList are just mudding things up.
            _view.Target = _declarations.Items.SingleOrDefault(declaration =>
                IsSelectedDeclaration(selection, declaration) || IsSelectedReference(selection, declaration));
better.
03:17
oh, nice. _declarations contains duplicates.
03:28
hmm of course... there are multiple matches because everything inside a procedure also matches the procedure.
03:40
well problem one, I shouldn't have to care about the entire procedure's body - only for its name.
04:01
well well well
that's a nice workaround!
instead of fighting with the selection glitch, I embrace it, and then instead of looking for a selection within a selection, I make a new Selection out of the first character of the selected code, and look for that instead.
^^ that's totally unclear
        private bool IsSelectedReference(QualifiedSelection selection, Declaration declaration)
        {
            return declaration.References.Any(r => r.Selection.ContainsFirstCharacter(selection.Selection));
        }

        private bool IsSelectedDeclaration(QualifiedSelection selection, Declaration declaration)
        {
            return declaration.QualifiedName.QualifiedModuleName == selection.QualifiedName
                   && (declaration.Selection.ContainsFirstCharacter(selection.Selection));
#CodeIsBetterThanThousandWords
04:21
well, everything works!
The value statement assignment rule listener sucks though. I can't come up with any meaningful names here:
        public override void EnterVsAssign(VBAParser.VsAssignContext context)
        {
            // one of these is null...
            var callStatementA = context.Parent.Parent.Parent as VBAParser.ICS_S_ProcedureOrArrayCallContext;
            var callStatementB = context.Parent.Parent.Parent as VBAParser.ICS_S_VariableOrProcedureCallContext;
            var callStatementC = context.Parent.Parent.Parent as VBAParser.ICS_B_MemberProcedureCallContext;
            var callStatementD = context.Parent.Parent.Parent as VBAParser.ICS_B_ProcedureCallContext;
#ButHeyItWorks
> closes #347
oh damn, I thought I had switched back to refactorings
back to next though, ... "FindAllReferences" isn't a refactoring
05:15
@Mat'sMug Hello, @Mat'sMug
Darn.
 
6 hours later…
11:39
Hi there @Shortstuff81000.
12:37
@Duga selection works. Target acquiring in a large project does reveal a few more kinks though
It's dumb. I'm ignoring the module you're in, so if there happens to be another procedure in another module at the same line position, and the other module comes up first, I'm returning that lol
#RubberduckDebuggingWorks
13:39
And I should be working in a separate Navigation branch for find all references
14:02
#RubberduckDebugging #Ftw
 
5 hours later…
19:05
Does it still count as "technical debt" if the code I'm writing will fail if it's run in the year 9900?
 
4 hours later…
23:00
RELOAD!
[retailcoder/Rubberduck] 3 commits. 1 opened issue. 1 closed issue. 2 issue comments.
[rolfl/MicroBench] 9 commits.
2
[Zomis/Prosit] 1 opened issue.
Who's the lurker?
@WXLSinfo take Rubberduck #UnitTesting API: early-bind for dev, late-bind and distribute for prod! Right hammer for the right nail, right?
@StackExchange learn how to one-box!
Seems like you guys are finally getting some competition again
3
7 mins ago, by Duga
[rolfl/MicroBench] 9 commits.
that's rolfl + me.

« first day (296 days earlier)      last day (2884 days later) »