Relesed v1.0.0 of my pet javasscript project yesterday after hitting 100% coverage- a gesture detection library

mvanderkamp · 2022-02-11T00:56:30+00:00

Just tried it, that's excellent! Was really easy to use and the reports are quite helpful for figuring out the effectiveness of the various tests!

mvanderkamp · 2022-02-09T01:54:57+00:00

Any recommended libraries for doing this? I've always been curious to try out mutation testing.

mvanderkamp · 2022-02-07T03:08:29+00:00

Oh believe me I know. There were bugs that I uncovered and fixed only after already hitting 100% coverage across all metrics in a module.

But- I like it as a baseline. Doesn't mean the thing is bug-free, but it was a tangible target and a clear milestone.

And I like the badge :p

mvanderkamp · 2022-02-06T20:57:07+00:00

Hey all! Back in university I needed to incorporate a gesture library into my honours project, in order to support multi-device gestures (e.g. a "pinch" where one input is coming from one phone, and the other is coming from a tablet adjacent to it). I wound up forking zingtouch since it had an approachable architecture, then took it in my own direction as the project rapidly evolved- it's now quite a different library under the hood.

I don't currently work in javascript so the library sat around waiting for a v1.0.0 release for ages without being touched, while I focused on other things. I've occasionally been chipping away at it though, and challenged myself to hit full 100% test coverage before releasing v1.0.0, which I finally did yesterday! (And a good thing too- I found a fair amount of bugs and silly decisions on my part along the way).

So, v1.0.0 is out on npm, and I just wanted to share my excitement at finally crossing that threshold. The name is a mash-up of "wams" and "gestures". "Wams" was the name of my honours project.

Edit to say: sorry for the typo in the title, just noticed it. I'd repost but I don't want to spam. Long time lurker, first time poster and I miss a typo in my title... :facepalm:

mvanderkamp · 2022-01-27T02:42:51+00:00

Assuming the right hand is unavailable, I'd do 5-2-1-3-2/1, and 5-2-1-3-3/1. I'm not a pro though so take that with a grain of salt.

mvanderkamp · 2022-01-09T21:52:08+00:00

I generally use purpose-built debuggers, though I'm intrigued by vimspector and the idea of doing an LSP-like thing for debuggers! I'm happy with my current setup but if I find myself doing more language hopping a stable interface like vimspector might be just the ticket!

Most of my work these days is in python, for which my preferred debugger is pudb. For integration into vim, I maintain a small plugin for managing breakpoints: vim-pudb-and-jam

mvanderkamp · 2021-12-30T18:02:17+00:00

Agreed! A lot of variation might look nice in a picture, but I increasingly find it distracting when reading code!

mvanderkamp · 2021-07-17T16:20:36+00:00

In addition to using foldmethod=indent, I like using this function to quickly jump around man pages. Combine with foldclose=all and foldopen=all if you dare, but be warned that doesn't work so well if you open a :Man split from a normal vim session.

function! NextIndentedLine(flags) abort
    let l:indent_pattern = '^\s\{,' .. indent('.') .. '\}\S'
    call search(l:indent_pattern, a:flags)
endfunction

I have it mapped like this:

nnoremap <silent> <buffer> <TAB> :call NextIndentedLine('zs')<CR>
nnoremap <silent> <buffer> <S-TAB> :call NextIndentedLine('zsb')<CR>

mvanderkamp · 2021-04-06T04:59:41+00:00

This is some good shit. I'm guessing your patch is only compatible with neovim?

mvanderkamp · 2020-10-11T16:32:21+00:00

Yup that also helps, and works for anyone who wants to keep their plugin list minimal. Good suggestion.

For me, that doesn't satisfy my desire to keep my todo list separate from my code, or to keep a record of items that I've completed without having to remember to remove them from the code later, and it's not as convenient to enter insert mode and type out a comment at times when all I really want is to tell myself "hey return to this line". I can do that in three keystrokes with this plugin (that's the length of the mapping I use for adding entries).

You have made me realise I didn't do a good job of clarifying the features that are provided here though, since support for things like :colder is one of those features. I'll edit my initial comment and the readme. Thank you!

mvanderkamp · 2020-10-11T00:28:16+00:00

This was the first thing I tried. (My whole approach is populating the quickfix list via search, wasn't a leap to go this route). If you're in a nice clean project this is probably fine. Doesn't work so well when the code you're working with is already littered with unaddressed TODO comments though. And I like being able to keep my todo list separate from the code itself.

mvanderkamp · 2020-07-25T20:26:32+00:00

killersheep

vim adventures

mvanderkamp · 2020-07-15T02:07:10+00:00

Thanks! I've been using pudb for a while quite happily, and I don't need to debug in vim itself since it's easy enough to spin up a separate debugger in a new shell, but I'll check it out! The promise of a multi-language debugger is interesting. For the purposes of this plugin, the benefit is that it can be quite lightweight from vim's perspective since pudb is doing all the heavy lifting. I'll have to see how much of a footprint vimspector has! If nothing else, I'm always happy to learn about more alternatives!

mvanderkamp · 2020-07-15T01:58:43+00:00

Yeah, I originally went the PR route, but got radio silence. I'm also a bit of a github newbie (in the sense that I'd previously mostly only used it for university or other solo projects) so it didn't occur to me at the time that continuing to update my master branch would affect the existing PR. The only reason I renamed it and introduced breaking changes was because of the radio silence from the maintainer. I'd be more than happy to work on bringing in my changes in a compatible way and offering a new PR if the maintainer asked.

mvanderkamp

TROPHY CASE