From f7bd2186f82cd30a621e7ad22103ed6d744b0537 Mon Sep 17 00:00:00 2001
From: Hopiu <ben.willi@gmail.com>
Date: Tue, 11 Apr 2017 08:45:30 +0200
Subject: [PATCH] Update widgets.py

How about adding those additional values to the template context? This allows having more options on how to render templates.
For example something like bootstrap tabs:
```
<!-- Nav tabs -->
<ul class="nav nav-tabs" role="tablist">
  <li class="nav-item">
    <a class="nav-link active" data-toggle="tab" href="#edit-{{attrs.id}}" role="tab">Edit</a>
  </li>
  <li class="nav-item">
    <a class="nav-link" data-toggle="tab" href="#preview-{{attrs.id}}" role="tab">Preview</a>
  </li>
</ul>

<!-- Tab panes -->
<div class="tab-content markdownx">
  <div class="tab-pane active" id="edit-{{attrs.id}}" role="tabpanel">
    {{ markdownx_editor }}
  </div>
  <div class="tab-pane" id="preview-{{attrs.id}}" role="tabpanel">
    <div class="markdownx-preview"></div>
  </div>
</div>
```
---
 markdownx/widgets.py | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/markdownx/widgets.py b/markdownx/widgets.py
index b5691a7..82dc126 100755
--- a/markdownx/widgets.py
+++ b/markdownx/widgets.py
@@ -71,6 +71,9 @@ class MarkdownxWidget(forms.Textarea):
 
         return template.render({
             'markdownx_editor': widget,
+            'name': name,
+            'value': value,
+            'attrs': attrs,
         })
 
     @staticmethod