@em.b wrote:
I'm prototyping a simple frontend that needs to send search queries to a backend API that ultimately ends up querying a search engine. The returned payload are not records per se but the results of the search query.
What's the right way to handle this in ember? It seems that the expected approach is to define models that map to 'records' that are already known in some kind of RDBMS, and URLs are automatically generated to map to these records by id. However, in the search example, the paradigm is much different in that there are no predefined records - we only know what will be returned after the user has submitted a search query.
Can someone explain the best way to handle this problem in ember? Do I need models that map to the different elements of each returned search query? Do I need to write a custom adapter to handle this type of query to the backend?
Thanks.
Posts: 4
Participants: 2