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

questionAnswers filtered by question paths onSubmit #85

Closed
geekyme opened this issue Mar 18, 2017 · 2 comments
Closed

questionAnswers filtered by question paths onSubmit #85

geekyme opened this issue Mar 18, 2017 · 2 comments
Labels

Comments

@geekyme
Copy link

geekyme commented Mar 18, 2017

Current behavior

In the demo, http://winterfell.andrewhathaway.net/, I first executed the path of an unsubscribed user. Therefore creating a json payload below:

screen shot 2017-03-18 at 8 31 08 pm

After that, I click back and executed the path of a subscribed user. And I see the json payload below:

screen shot 2017-03-18 at 8 32 11 pm

Expected behavior

The printed json payload should only contain data relevant to executed path. ie. I should not see any of the reg-* fields.

@andrewhathaway
Copy link
Owner

Hi @geekyme, yes you are correct. This, sadly, has been in from the start. I'll have to spend some time looking in to the issues for this project, PRs are accepted too!

@andrewhathaway
Copy link
Owner

Closing due to dupe (#5).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants