Skip to content

Commit

Permalink
V0.5.1 (#22)
Browse files Browse the repository at this point in the history
* fix template tag name

* Revert "fix template tag name"

This reverts commit 04b3040.

* DOC: update plotly_item to plotly_app

* Bump version to 0.5.1

Bump version to 0.5.1
  • Loading branch information
GibbsConsulting committed Jul 27, 2018
1 parent 09c56ab commit c71e864
Show file tree
Hide file tree
Showing 7 changed files with 7 additions and 7 deletions.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -108,7 +108,7 @@ templates:
```jinja2
{% load plotly_dash %}
{% plotly_item name="SimpleExample" %}
{% plotly_app name="SimpleExample" %}
```

The registration code needs to be in a location
Expand Down
2 changes: 1 addition & 1 deletion django_plotly_dash/__init__.py
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,6 @@
and enables it to be served as part of a Django application.
'''

__version__ = "0.5.0"
__version__ = "0.5.1"

from .dash_wrapper import DjangoDash
2 changes: 1 addition & 1 deletion django_plotly_dash/templatetags/plotly_dash.py
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@

ws_default_url = "/%s" % pipe_ws_endpoint_name()

@register.inclusion_tag("django_plotly_dash/plotly_item.html", takes_context=True)
@register.inclusion_tag("django_plotly_dash/plotly_app.html", takes_context=True)
def plotly_app(context, name=None, slug=None, da=None, ratio=0.1, use_frameborder=False):
'Insert a dash application using a html iframe'

Expand Down
2 changes: 1 addition & 1 deletion docs/installation.rst
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ database::

./manage.py migrate

The ``plotly_item`` tag in the ``plotly_dash`` tag library can then be used to render any registered dash component. See :ref:`simple_use` for a simple example.
The ``plotly_app`` tag in the ``plotly_dash`` tag library can then be used to render any registered dash component. See :ref:`simple_use` for a simple example.

It is important to ensure that any applications are registered using the ``DjangoDash`` class. This means that any python module containing the registration code has to be known to Django and loaded at the appropriate time. An easy way to ensure this is to import these modules into a standard Django file loaded at registration time.

Expand Down
2 changes: 1 addition & 1 deletion docs/simple_use.rst
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,7 @@ in :ref:`templates <template_tags>`:
{%load plotly_dash%}
{%plotly_item name="SimpleExample"%}
{%plotly_app name="SimpleExample"%}
Direct use in this manner, without any application state or
use of live updating, is equivalent to inserting an ``iframe`` containing the
Expand Down
4 changes: 2 additions & 2 deletions docs/template_tags.rst
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ Importing the ``plotly_dash`` library provides the ``plotly_app`` template tag:
{%load plotly_dash%}
{%plotly_item name="SimpleExample"%}
{%plotly_app name="SimpleExample"%}
This tag inserts
a ``DjangoDash`` app within a page as a responsive ``iframe`` element.
Expand All @@ -45,7 +45,7 @@ This template tag has to be inserted on every page that uses live updating:
{%load plotly_dash%}
{%plotly_item ... DjangoDash instances using live updating ... %}
{%plotly_app ... DjangoDash instances using live updating ... %}
{%plotly_message_pipe%}
Expand Down

0 comments on commit c71e864

Please sign in to comment.