Those changes to the substance search system are needed in order to ease API implementation
[ ] autocomplete system stays as is but might need refactor, as it could be probably be shared with aliases API view
[x] substance view routing is made strict and should not handle names or aliases anymore. it should be on-par with what will be used in API substance view routing
[x] GETsearch view without parameters serves current substance search form
[x] substance search logic is handled in manager, as those functions are complex for now they may need a bit of refactoring
[x] write unit tests for the search logic
[x] GET request with a query parameter populates the form server-side
if form is valid and manager returns an entry, perform a permanent redirect to this entry page
if form is not valid or manager cannot find a match, render the form again (current behavior)
Those changes to the substance search system are needed in order to ease API implementation
substance
view routingGET
search
view without parameters serves current substance search formGET
request with a query parameter populates the form server-side