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
{{ message }}
This repository has been archived by the owner on Sep 5, 2019. It is now read-only.
Most search properties are currently defined on the ORM model inside various onegov.* modules. I'm not yet sure this is a good idea, because we probably want different search properties for different applications.
Since we do not have different applications yet, this is currently not a pressing issue. But I think we should change this to a model where applications register models they would like to have search, alongside some kind of adapter which receives the model instance and is supposed to return the actual values for the document stored in elasticsearch.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Most search properties are currently defined on the ORM model inside various onegov.* modules. I'm not yet sure this is a good idea, because we probably want different search properties for different applications.
Since we do not have different applications yet, this is currently not a pressing issue. But I think we should change this to a model where applications register models they would like to have search, alongside some kind of adapter which receives the model instance and is supposed to return the actual values for the document stored in elasticsearch.
The text was updated successfully, but these errors were encountered: