On another topic, I tried using the Source Control to make one of my ms-access projects into an new repository. Rubberduck is making the new repository but is not announcing that it has been successfully created.
[retailcoder/Rubberduck]retailcoder pushed commit 965d3c7e to next: fixed resolver to correctly pick up string-typed built-in functions (e.g. Chr$), and implemented quickfix for UntypedFunctionUsageInspection
[rubberduck-vba/Rubberduck]retailcoder pushed commit 965d3c7e to next: fixed resolver to correctly pick up string-typed built-in functions (e.g. Chr$), and implemented quickfix for UntypedFunctionUsageInspection
[retailcoder/Rubberduck]retailcoder pushed commit 92a69817 to next: added support for annotations in Declaration class; DeclarationSymbolsListener picks up @annotations in module declarations section and on the line right above a declaration.
…sListener picks up @annotations in module declarations section and on the line right above a declaration.
[rubberduck-vba/Rubberduck]retailcoder pushed commit 92a69817 to next: added support for annotations in Declaration class; DeclarationSymbolsListener picks up @annotations in module declarations section and on the line right above a declaration
> Unit tests discovery is still running off the remnants of the `Reflection` stuff that was originally written in VBA.
A recent commit allows us to discover test modules and methods off the parse results using *annotations* - something like this would select all test method procedures:
> The example code in #814 is using `Annotations.TestModule` and `Annotations.TestMethod` - and we will need more of them... one for practically every code inspection (#810), and whatever comes along in the future.
Let's regroup them all in one place, a bit like the `Tokens` static class.
@RubberDuck Trying to work with the source control. There is a comment in the wiki that source control is not meant to be a full source control system. It might be good to say explicitly what is does and what it does not. e.g. no diffing tool. I am only new so might be user error.
I have been using github.com/timabell/msaccess-vcs-integration for source control and it works well. It exports table defs, which rubberduck does not. IMO keeping track of table design should be in version control. If also exports query defs which can be useful.
I hope to support some of those things in the future, but Rubberduck is really meant to work across all office products, not just one of them like the other options.
I just find that the source control dialog seems non-responsive. I can't can get a commit confirmation, can't open the git .ignore file etc. Ok Cheers
@RubberDuck Could you post a few screen shots somewhere so I know what the contents of the text boxes in the source control look like when source control is working. That would help greatly. I would be happy to write a wiki page on how to use the source control, if I can get it working.
@AndrewM I think something might have gotten broken between 1.4 and 1.4.3 somewhere, but have had very little (no) time to confirm that or fix any of it. Screenshots can be found here. christopherjmcclellan.wordpress.com/2015/06/29/…
@Mat'sMug fair point, but I'd still like an answer to the question. Drives me frickin nuts not understanding it.
VBA Rubberducking
VBA Rubberducking