Jake Urban

https://github.com/stellar/stellar-protocol/issues/1057

https://github.com/stellar/stellar-protocol/issues/1056

https://github.com/stellar/stellar-protocol/issues/1056

https://github.com/stellar/stellar-protocol/issues/1057

Looks like there is an issue filed on `pytest-django` too: https://github.com/pytest-dev/pytest-django/issues/580 This also could be a django-specific, non-pytest related problem: https://code.djangoproject.com/ticket/32409

@reecexlm this issue belongs in stellar/django-polaris, can you (or @stfung77) move it there?

@stfung77 This is a great write-up. ### Command / Script I'd like to take step back and ask, do we really need this? My gut says "This is what Django's...

Hi @yuriescl, Why does `currentStep` need to be stored in the URL instead of in the users's session cookie or the database? For example, I could add two forms to...

Hi @yuriescl, you're right, you'd need the GET request to contain an indication that the user went back in that case. We can add a key, `url_args`, to the dictionary...

Actually, there would be a way for you to change the initial URL. Polaris provides a `DepositIntegration.interactive_url()` function that is called on every GET request to the interactive flow. ```python...