Looking for kitchen sink apps

[fkleuver]

I'm putting out this ask in public for any core team member or community member to contribute to.

I'm looking for any runnable Aurelia app, ranging from little more than 'Hello World' demos, to apps with deeply nested routing structures and custom elements, attributes, dynamic compilation and the sorts (the more complex, monkey-patchey using-private-apis-in-ways-you-shouldn't, the better)

My plan is to create a big collection of automated E2E tests using selenium/browserstack and unleash those tests on the vCurrent repos with different browsers and versions. This should give us a better means to keep an eye on backwards compatibility and detect breaking changes more easily. It also gives us a more thorough baseline to cross-check vNext backwards compatibility.

Just post a link to your github repos in the comments.
A brief description of what it is (if the repo name isn't self-explanatory) is appreciated but not required. Ultimately I'm just looking for code, code, and more code.

And if anyone is familiar with webdriverio and the page object pattern and has some time to spare to help out (example: https://github.com/aurelia/aurelia/blob/master/test/e2e/specs/todos/app.page.ts) do let me know :)

@EisenbergEffect @bigopon @davismj @jdanyow @jods4 @Alexander-Taran @zewa666 @StrahilKazlachev @Vheissu @JeroenVinke @huochunpeng @mobilemancer @AshleyGrant @eriklieben @ZHollingshead

There have been lots of "I will" replies but no actual links yet. Please, links :)

[davismj]

I am guilty of an "I will." I think the biggest problem with this, at least for vCurrent, is that complex dev tool arrangements, not complex applications, tends to be the source of regressions. In the router, for example, webpack vs other, push state vs hash change, etc. Things you can't capture in a single app.

[fkleuver]

@davismj Those differences can be captured by consolidating some of these kitchen sink apps and replicating them in small variations for different bundlers. Don't worry about the edge cases that cannot be captured by single apps, I'm just asking for code so I can focus on surfacing those very differences you're talking about, not having to build apps too.
Even complex dev tools setup can themselves be automatically tested. I can setup a docker image with certain legacy stuff in them to go a few years back in time, and just run an install to see if it all still works. Everything can be tested. Everything.

[fkleuver]

I'll get the ball rolling with a few I already had in mind:
https://github.com/gothinkster/aurelia-realworld-example-app

https://github.com/aurelia/app-ux-showcase
https://github.com/aurelia/skeleton-navigation

https://github.com/bigopon/aurelia-monopoly
https://github.com/bigopon/aurelia-fractals
https://github.com/bigopon/aurelia-rainbow-spiral
https://github.com/bigopon/aurelia-sierpinski-triangle

https://github.com/jdanyow/aurelia-breeze-northwind
https://github.com/jdanyow/aurelia-dbmonster
https://github.com/jdanyow/aurelia-dropzone
https://github.com/jdanyow/aurelia-solitaire

https://github.com/EisenbergEffect/aurelia-composition-demo

https://github.com/monterey-framework/monterey

https://github.com/michaelbull/aurelia-typescript-webpack-starter
https://github.com/michaelbull/aurelia-hacker-news

[jbockle]

theres also https://builtwithaurelia.com/

[fkleuver]

@Vheissu I looked here to find all the repository urls associated with those projects but that list seems very dated. Do you have an up to date list of these projects where I can easily extract the repo urls? Cheers!

[CuddleBunny]

I had started to re-build my portfolio site with Aurelia. The main project is in Azure DevOps but I've pushed a mirror to GitHub: https://github.com/CuddleBunny/portfolio. I've paused development since I got a job but will probably keep tinkering with it once I get settled. Eventually I intend to use it as a test bed for https://github.com/CuddleBunny/aurelia-office-ui-fabric. I am definitely looking forward to porting both to vNext once it is ready for early adoption.

Not sure if this is a good candidate for your testing scenarios since it uses ASP.NET Core but thought I'd throw something up anyways.

[fkleuver]

@CuddleBunny That's perfect, thank you! The fact that it uses ASP.NET Core is only better because if anything that's a scenario we want to make much more robust and easier to work with in vNext. I'll definitely use that app as a source for some good test cases :)