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

[Emails] Display variables available in the context for every signal #2482

Closed
pbanaszkiewicz opened this issue Jul 21, 2023 · 0 comments · Fixed by #2491
Closed

[Emails] Display variables available in the context for every signal #2482

pbanaszkiewicz opened this issue Jul 21, 2023 · 0 comments · Fixed by #2491
Assignees

Comments

@pbanaszkiewicz
Copy link
Contributor

As a user I want to be able to see what variables, and with what type, are available in the email template body context.

@pbanaszkiewicz pbanaszkiewicz self-assigned this Jul 21, 2023
pbanaszkiewicz added a commit that referenced this issue Jul 26, 2023
pbanaszkiewicz added a commit that referenced this issue Jul 26, 2023
pbanaszkiewicz added a commit that referenced this issue Jul 28, 2023
pbanaszkiewicz added a commit that referenced this issue Jul 28, 2023
pbanaszkiewicz added a commit that referenced this issue Jul 28, 2023
pbanaszkiewicz added a commit that referenced this issue Jul 28, 2023
Using mocks was necessary because with
metaprogramming Django changes
Model.__class__ to ModelBase and therefore
(only in these tests!) it wasn't possible to use
Person or other models.

A trick was to use MagicMock with `.__class__.__name__`
attribute overwritten.
pbanaszkiewicz added a commit that referenced this issue Aug 5, 2023
pbanaszkiewicz added a commit that referenced this issue Aug 5, 2023
pbanaszkiewicz added a commit that referenced this issue Aug 5, 2023
pbanaszkiewicz added a commit that referenced this issue Aug 5, 2023
pbanaszkiewicz added a commit that referenced this issue Aug 5, 2023
Using mocks was necessary because with
metaprogramming Django changes
Model.__class__ to ModelBase and therefore
(only in these tests!) it wasn't possible to use
Person or other models.

A trick was to use MagicMock with `.__class__.__name__`
attribute overwritten.
pbanaszkiewicz added a commit that referenced this issue Aug 5, 2023
pbanaszkiewicz added a commit that referenced this issue Aug 11, 2023
pbanaszkiewicz added a commit that referenced this issue Aug 11, 2023
Updated sections containing variables available in template body.
pbanaszkiewicz added a commit that referenced this issue Aug 11, 2023
pbanaszkiewicz added a commit that referenced this issue Aug 11, 2023
pbanaszkiewicz added a commit that referenced this issue Aug 11, 2023
pbanaszkiewicz added a commit that referenced this issue Aug 11, 2023
Using mocks was necessary because with
metaprogramming Django changes
Model.__class__ to ModelBase and therefore
(only in these tests!) it wasn't possible to use
Person or other models.

A trick was to use MagicMock with `.__class__.__name__`
attribute overwritten.
pbanaszkiewicz added a commit that referenced this issue Aug 11, 2023
pbanaszkiewicz added a commit that referenced this issue Aug 11, 2023
pbanaszkiewicz added a commit that referenced this issue Aug 11, 2023
Updated sections containing variables available in template body.
pbanaszkiewicz added a commit that referenced this issue Aug 11, 2023
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 a pull request may close this issue.

1 participant