Testers wanted for port of the Aurelia Table plugin to v2

vNext
1

I wanted to see how difficult it would be to port over a v1 plugin to Aurelia 2 and the first plugin I opted for is a beloved community favourite: Aurelia Table. This is the first time I’ve ported over a non-core plugin to v2 and I will have a write up on this shortly, but I am looking for people to test it out.

The repository complete with instructions can be found here:

The plugin is available on Npm as aurelia2-table

Please let me know if you find any bugs. This port took around 30 minutes to finish (a true testament to Aurelia 2). Some of the original API’s were changed to use new features like the @watch decorator and whatnot.

6 Likes
2

I’m on board to test the auerlia-table and extremely happy to see all the activty as this has alleviated my converns about the future of AU2. I’ve looked at other solutions and really just want to use Auerlia.
Go AU2
John

4 Likes
3

My first test raised this error

    at aurelia2-table.es.js:15
    at ComputedWatcher.compute (watchers.ts:90)
    at ComputedWatcher.$bind (watchers.ts:60)
    at Controller.bind (controller.ts:513)
    at Controller.activate (controller.ts:504)
    at Controller.attach (controller.ts:604)
    at Controller.bind (controller.ts:534)
    at Controller.activate (controller.ts:504)
    at ComponentAgent.activate (component-agent.ts:77)
    at viewport-agent.ts:489
(anonymous) @ aurelia2-table.es.js:15
compute @ watchers.ts:90
$bind @ watchers.ts:60
bind @ controller.ts:513
activate @ controller.ts:504
attach @ controller.ts:604
bind @ controller.ts:534
activate @ controller.ts:504
activate @ component-agent.ts:77
(anonymous) @ viewport-agent.ts:489
run @ router.ts:322
(anonymous) @ viewport-agent.ts:487
invoke @ util.ts:44
pop @ util.ts:34
start @ util.ts:59
activate @ viewport-agent.ts:499
swap @ viewport-agent.ts:513
(anonymous) @ router.ts:843
invoke @ util.ts:44
pop @ util.ts:34
start @ util.ts:59
(anonymous) @ router.ts:862
run @ router.ts:328
run @ router.ts:802
enqueue @ router.ts:724
load @ router.ts:589
start @ router.ts:480
(anonymous) @ configuration.ts:54
run @ app-task.ts:101
(anonymous) @ app-root.ts:151
runAppTasks @ app-root.ts:149
(anonymous) @ app-root.ts:133
onResolve @ functions.ts:547
(anonymous) @ app-root.ts:132
onResolve @ functions.ts:547
(anonymous) @ app-root.ts:131
onResolve @ functions.ts:547
activate @ app-root.ts:130
(anonymous) @ aurelia.ts:94
onResolve @ functions.ts:547
start @ aurelia.ts:89
(anonymous) @ main.js:32
O @ space.js:258
Promise.then (async)
onResolve @ functions.ts:545
(anonymous) @ aurelia.ts:94
onResolve @ functions.ts:547
start @ aurelia.ts:89
(anonymous) @ main.js:32
O @ space.js:258
Promise.then (async)
r @ space.js:314
(anonymous) @ index.js:350
Promise.then (async)
(anonymous) @ index.js:349
req @ index.js:112
r @ space.js:199
(anonymous) @ index.js:558
i @ promise-utils.js:29
h @ promise-utils.js:42
M @ index.js:551
(anonymous) @ index.js:754
setTimeout (async)
z @ index.js:754
(anonymous) @ index.js:748
(anonymous) @ index.js:762
Show 13 more frames```
1 Like
4

@johntom Would you mind creating an issue on the repo above, please? I’d love to know what setup you’re using (Webpack, TypeScript and so on).

1 Like
5

In process now and I’m using javascript with dumber.

1 Like