VBA Rubberducking

Duga

12:00 AM

RELOAD!

[banane-io/PDB] 3 commits. 38 additions. 37 deletions.

[rubberduck-vba/Rubberduck] 1 issue comment.

Duga

12:17 AM

[rubberduck-vba/Rubberduck] bclothier commented on Rubberduck.Parsing/VBA/ReferenceResolveRunnerBase.cs of pull request #3893: Improve resolution for ambiguous names WRT scoping

[rubberduck-vba/Rubberduck] bclothier added label PR-Status: WIP to pull request #3893: Improve resolution for ambiguous names WRT scoping

Hosch250

12:59 AM

@IvenBach Self-review point #1. My JS is entirely too complicated.

For example, I have two pages that support drag/drop: the game board and the board editor.

IvenBach

@Hosch250 I never dug that deep. I avoided anything that wasn't a .cs file.

Hosch250

OK.

I'll still post it anyway because this is higher-level design decisions.

IvenBach

I may have a future win in my battle with #Words.

Hosch250

They both have much the same structure, but I want very specific behavior on each to make it as easy as possible to use. This conflicting behavior led to a ton of checks as to which page I'm on.

IvenBach

Got my duckling watching Schoolhouse Rock videos and I'm understanding the conjunction junction song.

Hosch250

1:02 AM

I decided that regardless of the structure, I would split it out into two files and maybe pull a few functions out with duplicated logic and stick it in one of them.

Cool. I'm hoping the storm that's coming up will be a really, really good one.

And glad it's weekend :)

IvenBach

Storm?

Hosch250

Thunderstorm.

I love them. They are so wild and primitive.

One of these days, I want to go storm chasing and see tornados and all.

Maybe even weather a hurricane.

Also:

4

Q: A term for a situation when something illegal, unjust, immoral and socially unacceptable becomes a standard pattern of an individual's behavior

When I was a teen, in a summer camp we enjoyed a sort of game that we played during so-called naptime after the midday meal. Split into pairs, the boys decided who would be horses and who horsemen, then the latter, blindfolded and having a pillow in their hands, mounted their companions and the f...

Hosch250

2:16 AM

Next up: clean up the game board drag/drop and re-simplify it.

And then rework the server logic a bit and implement the AI server-side.

And finally, wire up the "savable" interaction with a game through websockets instead of AJAX.

this

2:56 AM

@MathieuGuindon so I got to thinking.... the duck isn't meta enough.

Mathieu Guindon

@this oooh nice!!

this

figured that was more efficient at enforcing a certain code standard than some lengthy wiki article that nobody'll read. :)

one use Max definitely will like is guarding against chained member access w/ SCW/RCWs

IvenBach

3:42 AM

@this I see the arrows but don’t know their significance.

this

The new project RubberduckCodeAnalysis is a roslyn code analyzer where we can write our custom rule.

that error you saw is one of our own making

in other words, the ducky is rubberducking itself.

IvenBach

5:13 AM

That’s interesting. One day I’ll undwrstand how that’s possible. But not tonight. Sleep time. Night pond.

QHarr

5:23 AM

night

Duga

11:37 AM

[rubberduck-vba/Rubberduck] bclothier commented on RubberduckTests/Symbols/DeclarationFinderTests.cs of pull request #3893: Improve resolution for ambiguous names WRT scoping

Duga

11:54 AM

[rubberduck-vba/Rubberduck] bclothier synchronized pull request #3893: Improve resolution for ambiguous names WRT scoping

[rubberduck-vba/Rubberduck] [codecov[bot]](github.com/apps/codecov) commented on pull request #3893: Improve resolution for ambiguous names WRT scoping

> # [Codecov](https://codecov.io/gh/rubberduck-vba/Rubberduck/pull/3893?src=pr&el=h1) Report
> Merging [#3893](https://codecov.io/gh/rubberduck-vba/Rubberduck/pull/3893?src=pr&el=desc) into [next](https://codecov.io/gh/rubberduck-vba/Rubberduck/commit/1b1fe5cb0a9f3f17e4016128b4808fda16af7982?src=pr&el=desc) will **decrease** coverage by `0.12%`.
> The diff coverage is `100%`.

```diff
@@ Coverage Diff @@
## next #3893 +/- ##
=========================

[rubberduck-vba/Rubberduck] bclothier removed label PR-Status: WIP from pull request #3893: Improve resolution for ambiguous names WRT scoping

[rubberduck-vba/Rubberduck] bclothier removed label PR-Status: Review Requested from pull request #3893: Improve resolution for ambiguous names WRT scoping

[rubberduck-vba/Rubberduck] bclothier synchronized pull request #3893: Improve resolution for ambiguous names WRT scoping

[rubberduck-vba/Rubberduck] [codecov[bot]](github.com/apps/codecov) commented on pull request #3893: Improve resolution for ambiguous names WRT scoping

> # [Codecov](https://codecov.io/gh/rubberduck-vba/Rubberduck/pull/3893?src=pr&el=h1) Report
> Merging [#3893](https://codecov.io/gh/rubberduck-vba/Rubberduck/pull/3893?src=pr&el=desc) into [next](https://codecov.io/gh/rubberduck-vba/Rubberduck/commit/1b1fe5cb0a9f3f17e4016128b4808fda16af7982?src=pr&el=desc) will **decrease** coverage by `0.12%`.
> The diff coverage is `100%`.

```diff
@@ Coverage Diff @@
## next #3893 +/- ##
=========================

this

@Duga that makes me sad - especially considering that the decrease came from an unrelated file. :\

Mathieu Guindon

@rubberduckvba is it possible to export only one, specific folder instead of the entire project?

Tweeted by kulasart on April 28, 2018 at 11:09 AM

Duga

[rubberduck-vba/Rubberduck] LNow opened issue #3972: Export specific folder instead of the entire project

> We have `@Folder` annotation, but it is useless when we want to export only part of the project.
It would be great if we could export only one, specific folder instead of entire project.

[rubberduck-vba/Rubberduck] build for commit 01a9683b on unknown branch: AppVeyor build succeeded

[rubberduck-vba/Rubberduck] Vogel612 added label feature-export to issue #3972: Export specific folder instead of the entire project

[rubberduck-vba/Rubberduck] Vogel612 added label enhancement to issue #3972: Export specific folder instead of the entire project

[rubberduck-vba/Rubberduck] Vogel612 added label up-for-grabs to issue #3972: Export specific folder instead of the entire project

[rubberduck-vba/Rubberduck] Vogel612 added label difficulty-02-ducky to issue #3972: Export specific folder instead of the entire project

[rubberduck-vba/Rubberduck] retailcoder added label difficulty-01-duckling to issue #3972: Export specific folder instead of the entire project

Mathieu Guindon

12:09 PM

lol I was going to label it 01/duckling

Duga

[rubberduck-vba/Rubberduck] retailcoder removed label enhancement from issue #3972: Export specific folder instead of the entire project

[rubberduck-vba/Rubberduck] retailcoder removed label difficulty-02-ducky from issue #3972: Export specific folder instead of the entire project

Mathieu Guindon

@Duga wtf github

Duga

[rubberduck-vba/Rubberduck] retailcoder removed label up-for-grabs from issue #3972: Export specific folder instead of the entire project

Vogel612

grr damn github transaction fuckups

Duga

[rubberduck-vba/Rubberduck] retailcoder removed label feature-export from issue #3972: Export specific folder instead of the entire project

[rubberduck-vba/Rubberduck] retailcoder added label enhancement to issue #3972: Export specific folder instead of the entire project

this

12:10 PM

Mat / Vogel -- The ducky has asked that you kindly stop labeling it. It hurts its feeling when you do that.

Duga

[rubberduck-vba/Rubberduck] retailcoder added label up-for-grabs to issue #3972: Export specific folder instead of the entire project

[rubberduck-vba/Rubberduck] retailcoder added label feature-annotations to issue #3972: Export specific folder instead of the entire project

[rubberduck-vba/Rubberduck] retailcoder added label good first issue to issue #3972: Export specific folder instead of the entire project

[rubberduck-vba/Rubberduck] retailcoder added label feature-export to issue #3972: Export specific folder instead of the entire project

Vogel612

@this luckily we're labeling issues, not ducky

this

;)

Duga

[rubberduck-vba/Rubberduck] LNow commented on issue #3972: Export specific folder instead of the entire project

> Exporting to a separate directories based on @Folder annotation would be also more than welcome.

[rubberduck-vba/Rubberduck] build for commit 4cc396e0 on unknown branch: AppVeyor build succeeded

this

3:06 PM

Loving this. Even though I'm the guy who wrote it, it called me out!

QHarr

5:42 PM

Eve pond. Anyone home?

Duga

10:41 PM

[rubberduck-vba/Rubberduck] tommy9 created pull request #3973: Move closer refactoring indent fix to merge tommy9/Rubberduck/MoveCloserIndentFix into rubberduck-vba/Rubberduck/next

> Fixes #3964

First line after insertion was given no indentation. This PR checks the indentation of the line prior to the insertion and adds padding so that the same indentation is preserved.

A reparse is also requested after the refactoring has completed.

Duga

10:55 PM

[rubberduck-vba/Rubberduck] [codecov[bot]](github.com/apps/codecov) commented on pull request #3973: Move closer refactoring indent fix

> # [Codecov](https://codecov.io/gh/rubberduck-vba/Rubberduck/pull/3973?src=pr&el=h1) Report
> Merging [#3973](https://codecov.io/gh/rubberduck-vba/Rubberduck/pull/3973?src=pr&el=desc) into [next](https://codecov.io/gh/rubberduck-vba/Rubberduck/commit/1b1fe5cb0a9f3f17e4016128b4808fda16af7982?src=pr&el=desc) will **increase** coverage by `0.01%`.
> The diff coverage is `100%`.

```diff
@@ Coverage Diff @@
## next #3973 +/- ##
=========================

[rubberduck-vba/Rubberduck] build for commit a556bb49 on unknown branch: 57.81% (target 0%)

[rubberduck-vba/Rubberduck] build for commit a556bb49 on unknown branch: AppVeyor build succeeded

[rubberduck-vba/Rubberduck] Vogel612 commented on pull request #3973: Move closer refactoring indent fix

> For the Record: When fixing the original bug I tried to implement this on the parse tree, but gave it up.
Directly accessing the codepane is discouraged, but I haven't found a clean way to do this ....

Transcript for