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
Issue: Currently the search.py script used to generate the config.search.json file used by the application. This script generates an array of search items which follow the format of [<id>,<name>,<lower-left-x>,<lower-left-y>,<upper-right-x>,<upper-right-y>], but this format is not used by the core library.
The lookahead service expects search items in the following format;
Since the search.py script doesn't generate search items in the expected format, the app has a mapping function to update these items when the search control is added. See AddSearch() method in the lode-viewer application.js file, for an example. Instead of having the client generate the required format, the expected format could be generated by the search.py.
Solution: Instead of having the client format the data for the app before using it, it would be better to generate data in the expected format. This change will require the following;
Update the search.py script to generate search items in the expected format
Re-generate the config.search.py using the updated search.py
Remove the map function in the AddSearch() method in the application.js file.
The text was updated successfully, but these errors were encountered:
Issue: Currently the
search.py
script used to generate theconfig.search.json
file used by the application. This script generates an array of searchitems
which follow the format of[<id>,<name>,<lower-left-x>,<lower-left-y>,<upper-right-x>,<upper-right-y>]
, but this format is not used by the core library.The lookahead service expects search items in the following format;
Since the
search.py
script doesn't generate search items in the expected format, the app has a mapping function to update these items when the search control is added. SeeAddSearch()
method in the lode-viewer application.js file, for an example. Instead of having the client generate the required format, the expected format could be generated by the search.py.Solution: Instead of having the client format the data for the app before using it, it would be better to generate data in the expected format. This change will require the following;
search.py
script to generate search items in the expected formatconfig.search.py
using the updatedsearch.py
AddSearch()
method in theapplication.js
file.The text was updated successfully, but these errors were encountered: