You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently NestBot commands and event handlers use markdown method for rendering user facing content. The formatting process is time consuming and somewhat cumbersome.
Describe the solution you'd like
The idea is to implement a some sort of template system that would allow writing the content in text files and convert it into properly formatted markdown before sending to a user.
It should recognize formatting for \n, <@user_id>, <#{OWASP_GSOC_CHANNEL_ID}> and similar values.
The text was updated successfully, but these errors were encountered:
Create a templates/ directory containing template files with pre-written message content, including dynamic placeholders (e.g., {{ user_id }}, {{ channel_id }}).
Template Engine:
Use a template engine like Jinja2 to render dynamic content. (Alternative engines like Mako can be considered also, but Jinja2 is widely used and well-supported.)
Rendering Process:
The template engine will process the templates, replacing placeholders with dynamic data, and output properly formatted content ready to be sent to Slack.
Is your feature request related to a problem? Please describe.
Currently NestBot commands and event handlers use
markdown
method for rendering user facing content. The formatting process is time consuming and somewhat cumbersome.Describe the solution you'd like
The idea is to implement a some sort of template system that would allow writing the content in text files and convert it into properly formatted markdown before sending to a user.
It should recognize formatting for
\n
,<@user_id>
,<#{OWASP_GSOC_CHANNEL_ID}>
and similar values.The text was updated successfully, but these errors were encountered: