dstore | data infrastructure framework , providing the tools | Database library

Cookies started work after setting, however just works for ourdomain.com

dataset.mount() actually returns a MountContext which has a mount_point attribute.

So:

img = cv2.imread(mounted_images.mount_point +’/my_file_name.jpg')

Should hopefully work.

You could do something like the following:

You can find documentation on Filtering here.

In your case, .contains() will not work because it is intended to work on values of array type. What you want to filter here is array of objects. Here is a quote from the doc link:

contains: Filters for objects where the specified property's value is an array and the array contains any value that equals the provided value or satisfies the provided expression.

In my opinion, the best way here is to override the filter method where you want to filter by team name. Here is some sample code:

I think Iheriting the dstore/Rest , by creating your custom MyRest.js class an adding headers in constructor will help you to pass token in constrictor then , do operations without using headers each time.

You new class should look like :

In the "Creating Builds" tutorial, it says:

You might be asking yourself "if we build everything we need into a layer, why do we worry about the rest of the modules?" If you were to only keep the layer files and not have the rest of the modules available, you would lose that as an option to keep your application working without having to do a whole build again to access those modules.

That said, I agree with you, it would be nice to be able to build a minimal distribution containing only the layers - because even though the browser may only download the dojo/dojo.js layer, it's annoying to have to distribute the big 100MB directory.

However, even if the build script only copied the layer files, the layers may need various resource files which are not declared in the AMD dependency graph (e.g. images or fonts).

In my dojo projects, I've usually resorted to manually specifying and copying the required to a "minimal build" directory at the end of my build script. As long as it's a small application, this is usually manageable. It is certainly a bit annoying and error-prone though, so if anyone knows of a better way to do what you're asking, I'd love to hear about it.

I finally fixed it.

It's very convoluted and very little documented all this mess. I had to dig into the browser debugger and dgrid/Rest source code a bit.

So the problem was all in my REST backend. It turns out dgrid does a GET before the PUT/POST requesting the item to be modified, and it does a GET with only one record by asking for the specific "id". It make sense.

Well, my backend would return an ARRAY with one element in it, in JSON format. This was the error! This is not properly parsed by dgrid and it led to the POST instead of PUT.

Once i fixed the GET backend to return a single JSON item instead of an array with one JSON item inside, dgrid started sending the correct PUTs.

You're using the most recent dstore, but an old dgrid. The < 1.x versions of dgrid did not support dstore, you can use a regular dojo/store/Memory instead. In dgrid < 1.x, you also needed a store property instead of collection.

This one has been tough! Below a working example.

First I switched from declarative to programmatic for the onClick function: declarative scripts are parsed by dojo, and as a consequence you cannot examine them (set break points, etc.) under the debugger (at least I don't know how to do that). So it seems to me good practice to avoid them.

Then, indeed the bug is due to re-instantiating the dgrid with the same id, so that you do need a way to detect that the dgrid already exists. But there is a trick: for dgrids to be properly handled by the dijit system, they need to be mixed in with the dijitRegistry extension. See here for details.

Then you can use registry.byId('grid2') to detect that the dgrid already exists.

Also I had to skip the respDataForDgrid part and used directly respJSON instead (may be due to a difference with your server side(?) - I used a simple text file with a json array on the server side).