Currently $fh.sec's keygen operation generates a random secret for the key. If I added a backwards compatible patch to allow for a custom secret would it be of use? We need it in an application we're working on.

Following the example in the docs:

var dataset_id = 'tasks';

// Configuration options object.
// These override the options passed to init.
var options = {
"sync_frequency": 30 // Sync every 30 seconds for the 'tasks' dataset
};

// Parameters object to be passed to the cloud sync service.
// It will be passed to the dataHandler when listing dataset on the back end.
// If the default MBaaS cloud implementation is used (which uses $fh.db for data handlers), all the valid list options can be used here.
// For example, to list the tasks that are assigned to a user called "Tom", the query params should be
var query_params = {
"eq": {
"assigned": "Tom"
}
};

// Extra params that will be sent to the back-end data handlers.
var meta_data = {};
$fh.sync.manage(dataset_id, options, query_params, meta_data, function(){
console.log('dataset ' + dataset_id + ' is now managed by sync');
});

Ref: https://access.redhat.com/documentation/en-us/red_hat_mobile_application_platform_hosted/3/html-single/client_api/#fh-sync

Code implementation:

Hey,

Currently when making a FH.Cloud call the result of FH.getCloudParams is injected to the body/query. This is a highly intrusive behaviour that would be unwanted by people building an API in express since they have to deal with removing these from a query/body.

Placing these in the headers would be much cleaner and it appears we do that. I'll take a look to see why this is not being added to my FH.Cloud call headers, but would we be open to removing or adding a config option to prevent the FH.getCloudParams from being injected into user queries/bodies?

@wei-lee

I installed this module via npm into a project and then I tried to create my vendor bundle like so:

browserify -o www/dist/vendor.js -r fh-js-sdk -r react -r react-redux -r redux

Doing so results in an error like so being generated when browserify tries to package in fh-js-sdk due to the transforms required:

Error: Cannot find module 'browserify-shim' from '/workspaces/fh/my-app/node_modules/fh-js-sdk'

Currently I've found two solutions:

1. Install browserify-shim in my project
2. Install browserify-shim inside the node_modules of fh-js-sdk

I would suggest fixing by setting browserify-shim as a dependency or peerDependency of fh-js-sdk. Thoughts?

This is related to this PR: #213

When the connection tag is disabled, all the parameters passed to the error callback, including req, are apparently undefined. That PR assumes that req is defined, even though there's an explicit check for req not being there a couple lines above it. Line 86 in initializer.js thus throws a null pointer instead of calling the callback with the appropriate error.

https://github.com/feedhenry/fh-js-sdk/blob/2.23.0/src/modules/initializer.js#L86

I'd like to know if it would be ok to change the way handleError works when called in the event of an AJAX error.

Currently my express application returns a specific response format for all requests, even when I return a 500 error for example. When I return this 500 the SDK smarts kick in and parse it. As I don't conform to the format it expects, the errraw returned to the failure callback is undefined, but I need the errraw to present a useful error message to users.

I'd like to propose changing this line to something like:

errraw = res.error || res.msg || res;

This would mean that if a request doesn't have an error or msg result, such as in my case, it will still be returned to the error callback as a user would expect. I believe this would retain compatibility with previous applications too so it's safe.

For example, we are building an admin app for our services hosted in Feed Henry, and we want to enable the users to toggle between the different environments we have set up on the Feed Henry side of things. So, we have fhconfig-dev.json, fhconfig-stage.json and fhconfig-production.json. Is there any way we can init the fh library using one of those files? And then maybe also have a way to re-init with a different file at runtime? That way the user can pick their environment from a drop down and then view the data from that environment, all dynamically within the same page. Is this possible? If not, can it be added in as a feature?

Hello is it possible to emit 'fhcloudready' event like so:
....
module.exports = {
"boxprefix": "/box/srv/1.1/",
"sdk_version": "2.0.3-alpha",
"config_js": "fhconfig.json",
"INIT_EVENT": "fhinit",
"FH_READY_EVENT":"fhready"
};
....
events.emit(constants.FH_READY_EVENT);
logger.info("fh cloud is ready");
...
That way on you can listen to this like so:
$fh.on('fhready',function(){
console.log('CLOUD IS READY EVENT EMITED');
});

Thanks a lot.