Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Templating followup (for #104): Check new template name in first step and warn for invalid or potentially missing variables #125

Open
9 tasks
LucaBernstein opened this issue Apr 10, 2022 · 0 comments
Labels
Bot enhancement New feature or request

Comments

@LucaBernstein
Copy link
Owner

LucaBernstein commented Apr 10, 2022

Followup to #104

  • Check for template name conflicts in first step, adapt message in second step
  • Make sure that template size is not more that MAX_MSG_SIZE/2 for the start. (log as WARNING if app encounters larger one)
  • Do vars check: Warn for anything potentially missing or unknown
  • Automatically add space to tag field if rune before tag is not a space
  • Check and possibly improve code coverage
  • Think about template suggestions following /t
  • Allow alias desc for description in the template vars
  • Allow deletion of multiple templates at once: /t rm a b c
  • Add ${tag} variable to suggestions
@LucaBernstein LucaBernstein added the enhancement New feature or request label Apr 10, 2022
@LucaBernstein LucaBernstein self-assigned this Apr 10, 2022
@LucaBernstein LucaBernstein changed the title Check new template name in first step and warn for invalid or potentially missing variable Templating followup (for #104): Check new template name in first step and warn for invalid or potentially missing variables Apr 11, 2022
@LucaBernstein LucaBernstein removed their assignment Apr 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bot enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant