Dan Swain

> Must admit, I would personally advise against that method, as it comes with some security tradeoffs. For example, I could make your life difficult trying to get into your...

Could be, but the Jasmine code looks like it attempts to provide for a blank dictionary if no environment options are specified: env = options.env || {} Seems like if...

I submitted a pull request to the Jasmine project with the above proposed fix.

Not sure why, but my pull request for the above failed the CI. However, **I MIGHT have found the error** - in lines 51 through 54 of base.html, if you...

Here is an explanation that shows Jasmine's native structure: http://bittersweetryan.github.io/jasmine-presentation/#slide-24 http://bittersweetryan.github.io/jasmine-presentation/#slide-25 I think that an ideal setup would keep the native Jasmine structure as much as possible but provide for...

I would also suggest changing the template name from index.html to SpecRunner.html. This keeps with the Jasmine naming conventions as much as possible and is also more explicit as far...

You could disregard the comment above about multi-select. I see that the django_jasmine spec runner interface provides a clickable link which will run just one spec at a time.

I think that the "fixtures" explanation in the ReadMe could stand a little improvement - the explanation is not in complete sentences. Also, it seems that execution of the fixturesPath()...

It would be useful if the filename of the spec was placed as a group header above the specs within the file. It would also be nice if the "describe"...

Thanks @zodman. Don't know why I couldn't think of that, but you got me on the right track. Here's what I ended up with (had to use `id_for_label ` on...