origo-server-haninge-2024

Haninge's production build from the current master branch but with all the following additional branches merged:

• search-handle-multiple-databases
  • Allow multiple sub-models to be defined in dbconfig, which allows different connectors to be used as well (search from multiple databases as the same time).
• updated-node-mssql-syntax
  • Fix for mssql connections that's required after a dependency bump.
• title-option-in-dbconfig
  • Adding title to a search definition in dbconfig adds an extra "title" attribute in the response. Useful if there is no layer configured in the client to get a title from and the database table does not have a suitable column to use for title.
• multiple-search-fields-per-table
  • Possibility to define multiple search fields for a single table search definition in dbconfig, so that the table definition doesn't have to be repeated for every search field.
• limit-as-query-parameter
  • Handle a new query parameter &limit= that restricts the number of results returned per table (global limit set in dbconfig takes precedence).
• fix-missing-semicolon-and-refactor-oracle-type
  • Minor fix and refactors the "type" attribute handling in the oracle model to conform to the other models.
• (expose-individual-search-models-in-search)
  • Possibility to request search results from a specific sub-model defined in dbconfig (see "search-handle-multiple-databases").
  • Mostly replaced by "use-search-models-with-tag".
• custom-type-from-dbconfig-in-search
  • Adding customType to a table definition in dbconfig let's the type be set to something other than the table name, e g to match a layer name in the client.
• express-trust-proxy
  • New config option to set Express to "trust proxy" (see https://expressjs.com/en/guide/behind-proxies.html). Also removes the port number from the IP provided by the proxy, if present.
• Query-param-&c=true-to-override-query-param-limit
  • Handle &c=true as a new query parameter that overrides the &limit= parameter's value and instead returns the maximum allowed number of features in the limits set in dbconfig. This parameter is sent by the client's search control when a user presses the Enter key after getting a search result - which means the search control can be configured to use a limit for search suggestions, but then get the full result for the sidebar when pressing the Enter key.
• return-search-field-as-string
  • Fix for when the search field is a numeric column. Casts the search field as a string.
• use-search-models-with-tag
  • Mostly replaces "expose-individual-search-models-in-search" which used a URL path parameter, and instead uses the query parameter &tags=tag1,tag2,etc to fetch search results from all sub-models in dbconfig which have any of the supplied tags defined as a config option, e g tags: ["tag1", "test"].