Error if no credentials in ReactiveBase even if not using AppBase

[scottroot]

Affected Projects
React

Library Version: x.y.z
"@appbaseio/reactivesearch": "4.0.0-rc.3"

Describe the bug
With ReactiveBase, if there are no credentials provided for AppBase then there is a breaking error. Even if connecting to your own ES instance. I had to look up my credentials on appbase from a trial I did and enter that and it doesn't error now.

Expected behavior
I am connecting ReactiveSearch to my own ElasticCloud instance, not to AppBase so should not need appbase credentials in this component.

[parthvnp]

Happy to look into this and provide a fix.

[SavvyShah]

Only appbase instance is supported from v4 of library i.e enableAppbase is true always. You would either need to setup a gateway using reactivesearch-api or use Reactivesearch managed elasticsearch instance which would need no setup.

[noams-unbiased]

@SavvyShah is this a bug? will the package maintain support of the old way? or is this a breaking change that's here to stay?

[siddharthlatest]

@noams-unbiased This is a breaking change that's here to stay. ReactiveSearch UI kit requires use of ReactiveSearch cloud as a backend, more on this in the migration guide.

[rgb-panda]

Only appbase instance is supported from v4 of library i.e enableAppbase is true always. You would either need to setup a gateway using reactivesearch-api or use Reactivesearch managed elasticsearch instance which would need no setup.

@SavvyShah We've been using reactivesearch for a while, but are stuck on v3.45.0 since this change. Unfortunately we're not able to move away from elasticsearch native, but still want to leverage the enhancements in v4. Would using the reactivesearch-api as a gateway enable us to start using v4?