Skip to content

fix: drop duplicate trace button on strand detail (v0.3.8)#25

Merged
iamjohnnymac merged 2 commits into
mainfrom
fix/dedupe-trace-button-v0.3.8
May 19, 2026
Merged

fix: drop duplicate trace button on strand detail (v0.3.8)#25
iamjohnnymac merged 2 commits into
mainfrom
fix/dedupe-trace-button-v0.3.8

Conversation

@iamjohnnymac

Copy link
Copy Markdown
Owner

1-line template fix. After v0.3.7 wired the plugin slots, the 'Trace this core' button rendered twice on strand detail (inline include + PluginTemplateExtension both fired). Removed the inline include; extension is now the single source of truth.

… (v0.3.8)

v0.3.7 wired plugin_right_page into strand.html, which made the
StrandTraceButton PluginTemplateExtension fire and render the trace
button. The template also kept the pre-v0.3.1 inline include of the
button as a workaround, so the button rendered twice. Removed the
inline include + updated the extension's docstring.
The {# #} short comment is single-line only. My multi-line comment
about the trace button leaked subsequent lines into template
content, including a bare {% plugin_right_page %} call which Django
parsed as an actual tag invocation missing its obj argument — hence
the CI test failure 'plugin_right_page did not receive value for obj'.

Wrapped with {% comment %}{% endcomment %} block tags.
@iamjohnnymac iamjohnnymac merged commit 8f4bbfe into main May 19, 2026
2 checks passed
@iamjohnnymac iamjohnnymac deleted the fix/dedupe-trace-button-v0.3.8 branch May 19, 2026 02:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant