@andywww wrote:
Hi, I’m trying to persist some data in the URL because I don’t want to save to the database. Please can i get some feedback on my method?
<!-- On /language --> <select> <option value="slug1">text1</option> <option value="slug2">text2</option> <option value="slug3">text3</option> <option value="slug4">text4</option> </select> <!-- on submit transitions to --> /language/<slug1> <!-- hitting the above redirects to --> /language/<slug1>/signups/new <!-- slug is only persisted in the URL to enable me to do a lookup on the language model to return text for the signup form. The language is not persisted to the DB -->
The problem i’m having is I want to persist the slug selection across routes without saving any data to the database and have taken a nested routes approach to this so I can collect the slug from the URL to do the query and use the data returned in the signups template. I don’t want to nest the templates, however.
I’m a bit confused as to wether this isn’t the ember way and if not, would would one persist a selection so that it's value can be used later down the line?
Thanks in advance for any help!
Posts: 1
Participants: 1