analytics function doesn't send t object
#43
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Using v0.1.4, I'm getting this error:
where do you find this
tthing ? I am not using this lib anymore and struggle to find something about it, sorry :/It's from here:
6eafcf8dc6/lib/proto/parse-options.js (L10-L20)From what I can read, indeed it's not send. Not sure why I did that :(
This lib wasn't tested before 0.2, but it seems 0.2 is not working and nobody wants to contribute :/
any pointers on how we can fix 0.2?
I "just" splited the code into small pieces, in order to facilitate testing. It seems tests are broken and I think I didn't finish a test or something like that. Should not be a big deal, but "we" just need to find what is going wrong :/
Maybe you can try "npm install & npm test" and see what happens? :D
I can add you as a collab if you want
it breaks because one test has
t.failin it:https://github.com/MoOx/pjax/blob/master/tests/lib/switch-selectors.js#L6
no indication as to why it's made to fail though.
edit: its introduced here at #20
It's made to fail because there is no test written for it yet.
Switch Selectors also seems to be broken with issue #46 so I will look to fix that one and implement tests for it.
EDIT:
PR #52 patches switch-selectors.js test
So is this fixed now (sorry I am lazy)?
No I only fixed the failing test.
Not sure what the issue is in this one because the line of code referenced
doesn't seem to exist in the code base anymore.
On Tue, Jan 5, 2016 at 5:20 PM Maxime Thirouin notifications@github.com
wrote:
@moox, on a side note, may i ask why you're not using this library anymore?
for me: the alternatives are to use jquery.pjax and wiselinks, both of which rely on jQuery, which I'd prefer not to be a dependency.
I now only build webapps with React (for the last two years) :)
ah, haha, right
What about us poor legacy maintainers ...
grumbles
On Tue, Jan 5, 2016 at 5:26 PM Rico Sta. Cruz notifications@github.com
wrote:
This should be fixed by #59.