Tieson Trowbridge

No, the standard is the standard. The template is a template - you're not really supposed to just use it as-is. I'm sure that a pull-request fixing whatever is invalid...

This was reported previously, in #220

I don't see an issue with the navigation bar. The sidebar, on the other hand, seems to have an issue with the "expansion" indicators: 

The key word here is "template" - this project is just meant to be a set of components for building out an application. I'm not sure where demoing "state" management...

The flicker you're seeing is probably caused by the slight delay which occurs between when the page is rendered and when the JavaScript is run - you'll want this to...

Not sure what all has changed since @jayb611 posted their comment, but the only consistent fix I've found so far is slightly modifying the `buildData` function. In the compiled source,...

I'm assuming this happens because the background job is using something that has a dependency on a `EFCoreStoreDbContext` data context? If so, can the job be rewritten to remove that...

@Frankwayne It looks like @richardszalay enabled the Wiki feature - in lieu of a more dedicated docs site, adding something like this as a wiki entry would work (IMO). Assuming...

You could also get around that by using more specific paths: ``` "~/scripts/jquery.validate.min.js", "~/scripts/jquery.validate.unobtrusive.min.js", "~/scripts/jquery.validate.unobtrusive.bootstrap.js" ``` If you aren't planning on tweaking the plugin files, there really isn't a point...

For what it's worth, and for anyone else trying to figure this out, fabricjs-viewport works with fabricjs up through 1.6.0-rc.1 - after that, it fails silently. No idea why, either.