-
Notifications
You must be signed in to change notification settings - Fork 432
feat: email multiple recipients #14098
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
Merged
Merged
Changes from 8 commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
88ad981
plan generation
juleswg23 2d0a61c
parse and test new recipients field
juleswg23 3f396b1
delete claude files
juleswg23 5c23113
support write_yaml_metadata_block as a path for passing recipients
juleswg23 621feff
compress into fewer separate test files
juleswg23 65c6107
update changelog.
juleswg23 a5bf2c7
rename test
juleswg23 7a546b9
set email version in tests
juleswg23 ab01b32
parse emails with simplified regex (and add specific plaintext tests)
juleswg23 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
125 changes: 125 additions & 0 deletions
125
tests/docs/email/email-recipients-all-patterns-python.qmd
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,125 @@ | ||
| --- | ||
| title: Email Recipients - All Patterns (Python) | ||
| author: Jules Walzer-Goldfeld | ||
| format: | ||
| email: | ||
| email-version: 2 | ||
| --- | ||
|
|
||
| ```{python} | ||
| #| echo: false | ||
| import yaml | ||
| from IPython.display import Markdown | ||
|
|
||
| def write_yaml_metadata_block(**kwargs): | ||
| """Write YAML metadata block that will be parsed by Quarto.""" | ||
| yaml_content = yaml.dump( | ||
| kwargs, | ||
| default_flow_style=False, | ||
| allow_unicode=True, | ||
| sort_keys=False | ||
| ) | ||
| yaml_block = f"---\n{yaml_content}---\n" | ||
| return Markdown(yaml_block) | ||
| ``` | ||
|
|
||
| Test document demonstrating all recipient patterns with Python. | ||
|
|
||
| ```{python} | ||
| # Email 1: Static inline recipients | ||
| static_recipients = ["alice@example.com", "bob@example.com", "charlie@example.com"] | ||
| ``` | ||
|
|
||
| ::: {.email} | ||
|
|
||
| ::: {.subject} | ||
| Email 1: Static Inline Recipients | ||
| ::: | ||
|
|
||
| ::: {.recipients} | ||
| `{python} static_recipients` | ||
| ::: | ||
|
|
||
| ::: {.email-text} | ||
| Text version of email with static inline recipients. | ||
| ::: | ||
|
|
||
| First email with static inline recipients. | ||
|
|
||
| ::: | ||
|
|
||
| ```{python} | ||
| # Email 2: Conditional inline recipients | ||
| is_weekday = True # Fixed value for deterministic testing | ||
|
|
||
| if is_weekday: | ||
| conditional_recipients = ["weekday@example.com", "team@example.com"] | ||
| else: | ||
| conditional_recipients = ["weekend@example.com"] | ||
| ``` | ||
|
|
||
| ::: {.email} | ||
|
|
||
| ::: {.subject} | ||
| Email 2: Conditional Inline Recipients | ||
| ::: | ||
|
|
||
| ::: {.recipients} | ||
| `{python} conditional_recipients` | ||
| ::: | ||
|
|
||
| ::: {.email-text} | ||
| Text version of conditional recipients email. | ||
| ::: | ||
|
|
||
| Second email with conditional inline recipients. | ||
|
|
||
| ::: | ||
|
|
||
| ```{python} | ||
| #| output: asis | ||
| # Email 3: Metadata attribute pattern | ||
| metadata_recipients = ["metadata1@example.com", "metadata2@example.com"] | ||
| write_yaml_metadata_block(metadata_recipients=metadata_recipients) | ||
| ``` | ||
|
|
||
| ::: {.email recipients=metadata_recipients} | ||
|
|
||
| ::: {.subject} | ||
| Email 3: Metadata Attribute Pattern | ||
| ::: | ||
|
|
||
| ::: {.email-text} | ||
| This email uses the metadata attribute pattern. | ||
| ::: | ||
|
|
||
| Third email using metadata attribute pattern. | ||
|
|
||
| ::: | ||
|
|
||
| ```{python} | ||
| #| output: asis | ||
| # Email 4: Conditional metadata attribute pattern | ||
| is_admin = True # Fixed for testing | ||
|
|
||
| if is_admin: | ||
| admin_recipients = ["admin@example.com", "superuser@example.com"] | ||
| else: | ||
| admin_recipients = ["user@example.com"] | ||
|
|
||
| write_yaml_metadata_block(admin_recipients=admin_recipients) | ||
| ``` | ||
|
|
||
| ::: {.email recipients=admin_recipients} | ||
|
|
||
| ::: {.subject} | ||
| Email 4: Conditional Metadata Attribute | ||
| ::: | ||
|
|
||
| ::: {.email-text} | ||
| This email uses conditional metadata attribute pattern. | ||
| ::: | ||
|
|
||
| Fourth email using conditional metadata attribute pattern. | ||
|
|
||
| ::: |
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The approach here is parsing through various printed versions of list/vectors in Python + R and then extract the strings inside of them which (presumably) works (I haven't checked the tests yet, so maybe there actually are corner cases or bugs or something, but either way...).
What if, instead, we do the opposite: look for email addresses in the string and ignore everything else. My lua is not strong ™️ but Claude came up with the following:
What do you think of doing it that way?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I prefer this... I've updated this PR.