You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In all of our search forms (streets, addresses, names, etc.) we have a case where we display "no results found". The add button is usually displayed on the search results, rather than in the "no results found".
We need to make sure the add button shows up, especially when there are no results. Also; for our choosers, javascript needs to know to add a link to the "Add" action for whatever is being search for.
The text was updated successfully, but these errors were encountered:
I think, to make this happen, we need to update the output response for all searches that implement a non-HTML output.
Currently, I'm just returning the raw search results; however, I think I need to return more of a response object that includes the search results plus any actions the client is allowed to take. The actions would be defined as key=>value url=>labels. That way, the client js can draw the links to the actions when rendering the search results.
This means we need to standardize on a search result response for chooser operations.
In all of our search forms (streets, addresses, names, etc.) we have a case where we display "no results found". The add button is usually displayed on the search results, rather than in the "no results found".
We need to make sure the add button shows up, especially when there are no results. Also; for our choosers, javascript needs to know to add a link to the "Add" action for whatever is being search for.
The text was updated successfully, but these errors were encountered: