Fix/issue/512

[shifqu]

Description

Enrich global context in eval calls in CodeEvaluator._assert_code

Motivation behind this PR?

When writing an assert statement in scanapi which uses a list (or any other) comprehension, the code would fail.

What type of change is this?

Bugfix

Checklist

• I have added a changelog entry / my PR does not need a new changelog entry. Instructions.
• I have added/updated unit tests. Instructions.
• New and existing unit tests pass locally with my changes. Instructions
• I have self-documented code my changes by adding docstring(s) and comment(s). Instructions
• Current PR does not significantly decrease the code coverage and docstring coverage.
• My code follows the style guidelines of this project.
• I have run ScanAPI locally and manually tested my changes. Instructions.
• I have squashed my commits. Instructions.

Issue

Closes #512

[github-actions]

Thank you for supporting ScanAPI, and congratulations on your first contribution! A project committer will shortly review your contribution.

In the mean time, if you haven't had a chance please skim over the First Pull Request Guide which all pull requests must adhere to.

We hope to see you around!

[shifqu]

I had no idea black did not run on saving (I have this enabled on all my repositories by default and thus, did not pay real attention to it).

The black linting should pass now.

As for the DeepSource, it complains about using eval. Which it does so correctly, but this is the bread and butter of scanapi, so I was wondering how to add an exception to this hook.

[astenstrasser]

Hey @shifqu, thanks for the PR.
Looks great, nice approach :)

I notice there are some other commits included in the PR, not only your changed.
Could you please adjust it so we can merge?
Thanks!!

[shifqu]

Requested changes have been pushed. I also squashed the commits

[camilamaia]

Congrats on your first merged PR! 🌟 Thank you very much!

I am going to send you an invite to join the ScanAPI org on GitHub 🚀 We invite everyone that has contributed with a merged PR in any of our repositories. Here you can check our Contributing Guidelines so you can understand better how it works.

Check your email/GitHub notifications to find the invite. If you accept it, you will also be able to clone directly our repositories, without needing to fork them.

Welcome on board and once again, thank you! 🙇‍♀️