Giter Club home page Giter Club logo

app-search-reference-ui-react's Introduction

Contents


Getting started ๐Ÿฃ

This is a generated search experience created with Search UI.

To set up and run this project, follow the instructions below.

Requires npm.

Dependencies:

  • Node v16.13.0

One can leverage NVM to install Node before proceeding to start the application by running the following commands:

# Run this to install Node 16.13.0
nvm install 16.13.0

# Run this to use the installed Node version 
nvm use 16.13.0

Run the following commands to start this application:

# Run the `cd` command to change the current directory to the
# location of your downloaded Reference UI. Replace the path
# below with the actual path of your project.
cd ~/Downloads/app-search-reference-ui

# Run this to set everything up
npm install

# Run this to start your application and open it up in a new browser window
npm start

Usage

Updating configuration

The project is configured via a JSON config file. This file has been automatically generated for you when downloading this project. If you would like to make configuration changes, there is no need to regenerate this app from your App Search Dashboard. Additional configuration can be made by modifying that file.

You can simply open up the engine.json file, update the options, and then restart this app.

Configuration options

The following is a complete list of options available for configuration in engine.json.

option value type required/optional source
engineName String required Found in your App Search Dashboard.
endpointBase String required* (*) Elastic Enterprise Search deployment URL, example: "http://127.0.0.1:3002".
searchKey String required Found in your App Search Dashboard.
searchFields Array[String] required A list of fields that will be searched with your search term.
resultFields Array[String] required A list of fields that will be displayed within your results.
querySuggestFields Array[String] optional A list of fields that will be searched and displayed as query suggestions.
titleField String optional The field to display as the title in results.
urlField String optional A field with a url to use as a link in results.
sortFields Array[String] optional A list of fields that will be used for sort options.
facets Array[String] optional A list of fields that will be available as "facet" filters. Read more about facets within the App Search documentation.

Building and embedding

To embed this application into a website, it can be built into static assets using the following command:

npm run build

This will create two files in the build directory:

build/static/js/main.<hash>.js
build/static/css/main.<hash>.css

Include the built static assets as well as an element with id="root". For example:

<!DOCTYPE html>
<html lang="en">
  <head>
    <script defer="defer" src="/static/js/main.<hash>.js"></script>
    <link href="/static/css/main.<hash>.css" rel="stylesheet" />
  </head>
  <body>
    <div id="root" class="app-container"></div>
  </body>
</html>

Deploy and Share

This app can be easily published to any server as static assets and served. We recommend Netlify, but you have other options as well.

To deploy:

npm run build
npm install netlify-cli -g
netlify deploy # enter ./build as the deploy path

You'll then simply follow the command prompt to log into Netlify and deploy your site. This can be completed in just a few minutes.

External configuration

If you are embedding this app inside of another page, and you would like to source the configuration from outside of the engine.json file, you can simply write the configuration directly to window.appConfig.

If you are checking this project out directly from GitHub...

You can follow the previous steps, but then you will need to create and configure engine.json.

To do so, make a copy of engine.json.example, rename it to engine.json and configure it with your Engine's specific details.

cp src/config/engine.json.example src/config/engine.json

Customization

This project is built with Search UI, which is a React library for building search experiences. If you're interested in using this project as a base for your own, most of what you'll need can be found in the Search UI documentation.

FAQ ๐Ÿ”ฎ

Where do I report issues with this application?

If something is not working as expected, please open an issue.

Where else can I go to get help?

You can checkout the Elastic Enterprise Search community discuss forums.

License ๐Ÿ“—

Apache-2.0 ยฉ Elastic

app-search-reference-ui-react's People

Contributors

cee-chen avatar christophercutajar avatar dependabot[bot] avatar goodroot avatar jasonstoltz avatar jgr avatar joemcelroy avatar orhantoy avatar richkuz avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

app-search-reference-ui-react's Issues

problem in text alignment

Text alignment is at left. It should be at center.

Actual Behaviour
Screenshot from 2020-06-13 20-13-13

Expected Behaviour
Screenshot from 2020-06-13 20-12-47

Would you like to work on the issue?
Yes, I want to do that.

Does this work with Vue?

The Reference UI is great. I like how you can get the config straight from Elastic Cloud's App search.

I am using Nuxt (Vue). Is there a way to get this to work in Vue?

Grouping documents breaks pagination & more

The grouping features seems to break pagination, total results, and results per page when using the Reference UI or Search UI.

To reproduce, download the Reference UI/Search UI and apply a grouping rule to one of the fields:
"group": { "field": "doc_group" }

The total results, and results per page sections represent the amount results had they not been grouped together, I think this is a little misleading as the amount of visible documents would be considerably less.

The pagination has the same issue. Due to the app thinking there are more results to be shown, it calculates more pages than you need, then some of the pages show blank as there actually aren't that many results.

Include Link to Repository in the Downloadable Package

It would be fantastic to add a reference to this GitHub repository somewhere in the package, either in the README, or anywhere else you feel is appropriate. This will help people understand where to file Issues and provide feedback!

[Feature Request] Typeahead

It'd be great if the reference UI had typeahead. Maybe a config parameter with a list of fields queried for typeahead?

Failed to fetch CORS issue on Managed Swiftype

Hi when loading the reference ui from within the Swiftype dashboard we're receiving a CORS error:

Access to fetch at 'https://host-64fz8w.api.swiftype.com/api/as/v1/engines/rydale/search.json' from origin 'https://app.swiftype.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: The value of the 'Access-Control-Allow-Credentials' header in the response is '' which must be 'true' when the request's credentials mode is 'include'.

This is happening on all 3 of our live eCommerce sites during our black friday sales. I've had multiple customers call in having the same issue. I have contacted support via email, & community forums with no reply, status page has no update.

Please can we get someone looking into this!

Thanks

[Feature Request] Support SearchKey as an Environment Variable

Having the searchKey in the clear in engine.json is not the best approaches from a security point of view.

It would be great if the searchKey can be read at runtime from an environment variable.

As an example the AppSearchAPIConnector connector would be something like the following:

const connector = new AppSearchAPIConnector({
  searchKey: process.env.REACT_APP_APPSEARCH_SEARCHKEY,
  engineName,
  hostIdentifier,
  endpointBase
});

Would like to get your opinion on this before performing any work. Ready to submit a PR for this feature ๐Ÿ˜„

401 error

Hi,

I create an App search scaffold from enterprise-search on my server ( same network than my laptop)
I follow instruction to run the react app :

  • npm build
  • serve -s build

I success to show the application from my laptop ( firefox ) . From other computer or from google chrome, it ask for a "user" and "password" by telling "Your connexion is not private" ... I cannot understand

Build process failed

Hi there,

i tried to build the search-ui frontend in an empty local project. Got the app-search-reference-ui-react code as a zip package from the App Search dashboard, as suggested in the Readme in this repository.

System Win10

Installed and up to date
npm -v : 7.6.1
node -v: v15.11.0

Installed ms Build tools 2019 after first build attempt that failed because of missing MSBuildTools.
I tried:

  • reinstalling Node and NPM but no change to the problem.
  • running npm install node-sass manually with no success

I'm not sure how to debug this issue further. Can someone help me with this?

Terminaloutput:

npm ERR! code 1
npm ERR! path C:\xampp\htdocs\app-search-reference-ui-react-master\node_modules\node-sass
npm ERR! command failed
npm ERR! command C:\Windows\system32\cmd.exe /d /s /c node scripts/build.js
npm ERR! Building: C:\Program Files\nodejs\node.exe C:\xampp\htdocs\app-search-reference-ui-react-master\node_modules\node-gyp\bin\node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp verb cli [
npm ERR! gyp verb cli 'C:\Program Files\nodejs\node.exe',
npm ERR! gyp verb cli 'C:\xampp\htdocs\app-search-reference-ui-react-master\node_modules\node-gyp\bin\node-gyp.js',
npm ERR! gyp verb cli 'rebuild',
npm ERR! gyp verb cli '--verbose',
npm ERR! gyp verb cli '--libsass_ext=',
npm ERR! gyp verb cli '--libsass_cflags=',
npm ERR! gyp verb cli '--libsass_ldflags=',
npm ERR! gyp verb cli '--libsass_library='
npm ERR! gyp verb cli ]
npm ERR! gyp info using [email protected]
npm ERR! gyp info using [email protected] | win32 | x64
npm ERR! gyp verb command rebuild []
npm ERR! gyp verb command clean []
npm ERR! gyp verb clean removing "build" directory
npm ERR! gyp verb command configure []
npm ERR! gyp verb check python checking for Python executable "python2" in the PATH
npm ERR! gyp verb which failed Error: not found: python2
npm ERR! gyp verb which failed at getNotFoundError (C:\xampp\htdocs\app-search-reference-ui-react-master\node_modules\which\which.js:13:12)
npm ERR! gyp verb which failed at F (C:\xampp\htdocs\app-search-reference-ui-react-master\node_modules\which\which.js:68:19)
npm ERR! gyp verb which failed at E (C:\xampp\htdocs\app-search-reference-ui-react-master\node_modules\which\which.js:80:29)
npm ERR! gyp verb which failed at C:\xampp\htdocs\app-search-reference-ui-react-master\node_modules\which\which.js:89:16
npm ERR! gyp verb which failed at C:\xampp\htdocs\app-search-reference-ui-react-master\node_modules\isexe\index.js:42:5
npm ERR! gyp verb which failed at C:\xampp\htdocs\app-search-reference-ui-react-master\node_modules\isexe\windows.js:36:5
npm ERR! gyp verb which failed at FSReqCallback.oncomplete (node:fs:200:21)
npm ERR! gyp verb which failed python2 Error: not found: python2
npm ERR! gyp verb which failed at getNotFoundError (C:\xampp\htdocs\app-search-reference-ui-react-master\node_modules\which\which.js:13:12)
npm ERR! gyp verb which failed at F (C:\xampp\htdocs\app-search-reference-ui-react-master\node_modules\which\which.js:68:19)
npm ERR! gyp verb which failed at E (C:\xampp\htdocs\app-search-reference-ui-react-master\node_modules\which\which.js:80:29)
npm ERR! gyp verb which failed at C:\xampp\htdocs\app-search-reference-ui-react-master\node_modules\which\which.js:89:16
npm ERR! gyp verb which failed at C:\xampp\htdocs\app-search-reference-ui-react-master\node_modules\isexe\index.js:42:5
npm ERR! gyp verb which failed at C:\xampp\htdocs\app-search-reference-ui-react-master\node_modules\isexe\windows.js:36:5
npm ERR! gyp verb which failed code: 'ENOENT'
npm ERR! gyp verb check python checking for Python executable "python" in the PATH
npm ERR! gyp verb which succeeded python C:\Python39\python.EXE
npm ERR! gyp ERR! configure error
npm ERR! gyp ERR! stack Error: Command failed: C:\Python39\python.EXE -c import sys; print "%s.%s.%s" % sys.version_info[:3];
npm ERR! gyp ERR! stack File "", line 1
npm ERR! gyp ERR! stack import sys; print "%s.%s.%s" % sys.version_info[:3];
npm ERR! gyp ERR! stack ^
npm ERR! gyp ERR! stack SyntaxError: invalid syntax
npm ERR! gyp ERR! stack at ChildProcess.exithandler (node:child_process:326:12)
npm ERR! gyp ERR! stack at ChildProcess.emit (node:events:378:20)
npm ERR! gyp ERR! stack at maybeClose (node:internal/child_process:1067:16)
npm ERR! gyp ERR! stack at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5)
npm ERR! gyp ERR! System Windows_NT 10.0.19042
npm ERR! gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\xampp\htdocs\app-search-reference-ui-react-master\node_modules\node-gyp\bin\node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
npm ERR! gyp ERR! cwd C:\xampp\htdocs\app-search-reference-ui-react-master\node_modules\node-sass
npm ERR! gyp ERR! node -v v15.11.0
npm ERR! gyp ERR! node-gyp -v v3.8.0
npm ERR! gyp ERR! not ok
npm ERR! Build failed with error code: 1

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\marti\AppData\Local\npm-cache_logs\2021-03-09T09_55_25_819Z-debug.log

npm install of reference ui did not work - ?

Hello, I have local elasticsearch instance and local enterprise-search instance. In AppSearch dashboard (localhost:3002) I built a reference UI, and tried to install it (as per the README.md instruction) with npm install, however it does not seem to work (?). Below the terminal output:

(base) ae@machine:~/Downloads/app-search-reference-ui$ npm install
npm ERR! code 1
npm ERR! path /home/ae/Downloads/app-search-reference-ui/node_modules/node-sass
npm ERR! command failed
npm ERR! command sh -c node scripts/build.js
npm ERR! Building: /usr/bin/node /home/ae/Downloads/app-search-reference-ui/node_modules/node-gyp/bin/node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
npm ERR! make: Entering directory '/home/ae/Downloads/app-search-reference-ui/node_modules/node-sass/build'
npm ERR!   g++ '-DNODE_GYP_MODULE_NAME=libsass' '-DUSING_UV_SHARED=1' '-DUSING_V8_SHARED=1' '-DV8_DEPRECATION_WARNINGS=1' '-DV8_DEPRECATION_WARNINGS' '-DV8_IMMINENT_DEPRECATION_WARNINGS' '-D_LARGEFILE_SOURCE' '-D_FILE_OFFSET_BITS=64' '-D__STDC_FORMAT_MACROS' '-DOPENSSL_NO_PINSHARED' '-DOPENSSL_THREADS' '-DLIBSASS_VERSION="3.5.4"' -I/home/ae/.node-gyp/15.11.0/include/node -I/home/ae/.node-gyp/15.11.0/src -I/home/ae/.node-gyp/15.11.0/deps/openssl/config -I/home/ae/.node-gyp/15.11.0/deps/openssl/openssl/include -I/home/ae/.node-gyp/15.11.0/deps/uv/include -I/home/ae/.node-gyp/15.11.0/deps/zlib -I/home/ae/.node-gyp/15.11.0/deps/v8/include -I../src/libsass/include  -fPIC -pthread -Wall -Wextra -Wno-unused-parameter -m64 -O3 -fno-omit-frame-pointer -std=gnu++1y -std=c++0x -fexceptions -frtti -MMD -MF ./Release/.deps/Release/obj.target/libsass/src/libsass/src/ast.o.d.raw   -c -o Release/obj.target/libsass/src/libsass/src/ast.o ../src/libsass/src/ast.cpp
npm ERR! make: Leaving directory '/home/ae/Downloads/app-search-reference-ui/node_modules/node-sass/build'
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp verb cli [
npm ERR! gyp verb cli   '/usr/bin/node',
npm ERR! gyp verb cli   '/home/ae/Downloads/app-search-reference-ui/node_modules/node-gyp/bin/node-gyp.js',
npm ERR! gyp verb cli   'rebuild',
npm ERR! gyp verb cli   '--verbose',
npm ERR! gyp verb cli   '--libsass_ext=',
npm ERR! gyp verb cli   '--libsass_cflags=',
npm ERR! gyp verb cli   '--libsass_ldflags=',
npm ERR! gyp verb cli   '--libsass_library='
npm ERR! gyp verb cli ]
npm ERR! gyp info using [email protected]
npm ERR! gyp info using [email protected] | linux | x64
npm ERR! gyp verb command rebuild []
npm ERR! gyp verb command clean []
npm ERR! gyp verb clean removing "build" directory
npm ERR! gyp verb command configure []
npm ERR! gyp verb check python checking for Python executable "python2" in the PATH
npm ERR! gyp verb `which` succeeded python2 /usr/bin/python2
npm ERR! gyp verb check python version `/usr/bin/python2 -c "import sys; print "2.7.18
npm ERR! gyp verb check python version .%s.%s" % sys.version_info[:3];"` returned: %j
npm ERR! gyp verb get node dir no --target version specified, falling back to host node version: 15.11.0
npm ERR! gyp verb command install [ '15.11.0' ]
npm ERR! gyp verb install input version string "15.11.0"
npm ERR! gyp verb install installing version: 15.11.0
npm ERR! gyp verb install --ensure was passed, so won't reinstall if already installed
npm ERR! gyp verb install version is already installed, need to check "installVersion"
npm ERR! gyp verb got "installVersion" 9
npm ERR! gyp verb needs "installVersion" 9
npm ERR! gyp verb install version is good
npm ERR! gyp verb get node dir target node version installed: 15.11.0
npm ERR! gyp verb build dir attempting to create "build" dir: /home/ae/Downloads/app-search-reference-ui/node_modules/node-sass/build
npm ERR! gyp verb build dir "build" dir needed to be created? /home/ae/Downloads/app-search-reference-ui/node_modules/node-sass/build
npm ERR! gyp verb build/config.gypi creating config file
npm ERR! gyp verb build/config.gypi writing out config file: /home/ae/Downloads/app-search-reference-ui/node_modules/node-sass/build/config.gypi
npm ERR! gyp verb config.gypi checking for gypi file: /home/ae/Downloads/app-search-reference-ui/node_modules/node-sass/config.gypi
npm ERR! gyp verb common.gypi checking for gypi file: /home/ae/Downloads/app-search-reference-ui/node_modules/node-sass/common.gypi
npm ERR! gyp verb gyp gyp format was not specified; forcing "make"
npm ERR! gyp info spawn /usr/bin/python2
npm ERR! gyp info spawn args [
npm ERR! gyp info spawn args   '/home/ae/Downloads/app-search-reference-ui/node_modules/node-gyp/gyp/gyp_main.py',
npm ERR! gyp info spawn args   'binding.gyp',
npm ERR! gyp info spawn args   '-f',
npm ERR! gyp info spawn args   'make',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   '/home/ae/Downloads/app-search-reference-ui/node_modules/node-sass/build/config.gypi',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   '/home/ae/Downloads/app-search-reference-ui/node_modules/node-gyp/addon.gypi',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   '/home/ae/.node-gyp/15.11.0/include/node/common.gypi',
npm ERR! gyp info spawn args   '-Dlibrary=shared_library',
npm ERR! gyp info spawn args   '-Dvisibility=default',
npm ERR! gyp info spawn args   '-Dnode_root_dir=/home/ae/.node-gyp/15.11.0',
npm ERR! gyp info spawn args   '-Dnode_gyp_dir=/home/ae/Downloads/app-search-reference-ui/node_modules/node-gyp',
npm ERR! gyp info spawn args   '-Dnode_lib_file=/home/ae/.node-gyp/15.11.0/<(target_arch)/node.lib',
npm ERR! gyp info spawn args   '-Dmodule_root_dir=/home/ae/Downloads/app-search-reference-ui/node_modules/node-sass',
npm ERR! gyp info spawn args   '-Dnode_engine=v8',
npm ERR! gyp info spawn args   '--depth=.',
npm ERR! gyp info spawn args   '--no-parallel',
npm ERR! gyp info spawn args   '--generator-output',
npm ERR! gyp info spawn args   'build',
npm ERR! gyp info spawn args   '-Goutput_dir=.'
npm ERR! gyp info spawn args ]
npm ERR! gyp verb command build []
npm ERR! gyp verb build type Release
npm ERR! gyp verb architecture x64
npm ERR! gyp verb node dev dir /home/ae/.node-gyp/15.11.0
npm ERR! gyp verb `which` succeeded for `make` /usr/bin/make
npm ERR! gyp info spawn make
npm ERR! gyp info spawn args [ 'V=1', 'BUILDTYPE=Release', '-C', 'build' ]
npm ERR! make: g++: Command not found
npm ERR! make: *** [src/libsass.target.mk:160: Release/obj.target/libsass/src/libsass/src/ast.o] Error 127
npm ERR! gyp ERR! build error 
npm ERR! gyp ERR! stack Error: `make` failed with exit code: 2
npm ERR! gyp ERR! stack     at ChildProcess.onExit (/home/ae/Downloads/app-search-reference-ui/node_modules/node-gyp/lib/build.js:262:23)
npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:378:20)
npm ERR! gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12)
npm ERR! gyp ERR! System Linux 5.8.0-45-generic
npm ERR! gyp ERR! command "/usr/bin/node" "/home/ae/Downloads/app-search-reference-ui/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
npm ERR! gyp ERR! cwd /home/ae/Downloads/app-search-reference-ui/node_modules/node-sass
npm ERR! gyp ERR! node -v v15.11.0
npm ERR! gyp ERR! node-gyp -v v3.8.0
npm ERR! gyp ERR! not ok 
npm ERR! Build failed with error code: 1

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/ae/.npm/_logs/2021-03-25T08_41_24_575Z-debug.log

This is what's in the directory:

(base) ae@machine:~/Downloads/app-search-reference-ui$ tree
.
โ”œโ”€โ”€ bin
โ”‚ย ย  โ””โ”€โ”€ ensure_engine_config.sh
โ”œโ”€โ”€ LICENSE.txt
โ”œโ”€โ”€ logo-app-search.png
โ”œโ”€โ”€ NOTICE.txt
โ”œโ”€โ”€ package.json
โ”œโ”€โ”€ package-lock.json
โ”œโ”€โ”€ public
โ”‚ย ย  โ”œโ”€โ”€ favicon.ico
โ”‚ย ย  โ”œโ”€โ”€ index.html
โ”‚ย ย  โ””โ”€โ”€ manifest.json
โ”œโ”€โ”€ README.md
โ”œโ”€โ”€ scripts
โ”‚ย ย  โ””โ”€โ”€ build-no-chunks.js
โ””โ”€โ”€ src
    โ”œโ”€โ”€ App.js
    โ”œโ”€โ”€ config
    โ”‚ย ย  โ”œโ”€โ”€ config-helper.js
    โ”‚ย ย  โ”œโ”€โ”€ engine.json
    โ”‚ย ย  โ””โ”€โ”€ engine.json.example
    โ”œโ”€โ”€ index.js
    โ””โ”€โ”€ _tests_
        โ””โ”€โ”€ App.test.js

6 directories, 17 files

Sort Results label to Relevance

I would like to suggest changing the Sort Results label option in the sorting Select Box to Relevance, as choosing this option renders results based on the computed score. It'll make the sorting experience a little easier to digest.

Thanks!

Language

Hey guys!
Is there a way to translate every words to french?

not able to run on 'http://localhost:3000/'

getting error : An unexpected error occurred: Failed to fetch

engin.json details:

{
"endpointBase": "http://127.0.0.1:3002",
"engineName": "engine",
"hostIdentifier": "host-xXXXX",
"searchKey": "private-xxxxxxxxxxxxxx",
"searchFields": ["title", "states"],
"resultFields": ["id", "title", "states", "description", "visitors"],
"querySuggestFields": ["title"],
"titleField": "title",
"urlField": "https://host-x2hop8.api.swiftype.com",
"sortFields": ["title", "anotherField"],
"facets": ["states", "title"]
}

could you please help to resolve this error ?

Support for on-premise app-search

This app assumes that i'm using the swiftype service as the backend (i have my on premise app-search instance running), how i can make it work?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.