Assets API and new folder structure

batjko · April 22, 2016, 11:01am

Hi guys,

I am trying to follow the new recommended 1.3 folder structure and so don’t have one big client or server folder anymore, but instead a bunch of “modules”, under each of which there are client and server folders scoped to this one module/feature.

So now I want to load a static file from the server (e.g. myAwesomeQueryString.graphql), and so tried to follow the API documention for Assets.getText(), and thought I’d put it in private\myAwesomeQueryString.graphql.
However, this “private” folder is not in my app root, but instead within my module (i.e. some subfolder of the app).

And Meteor can’t seem to find it now, when I call

Assets.getText('myAwesomeQueryString.graphql');

I get Error: Unknown asset: myAwesomeQueryString.graphql now.

The API documentation tells me, the path it looks for is relative to the “private” folder, but of course there may be a bunch of them now, if I have one per module.
I wouldn’t want to have to pull them out into one root-level “private” folder again, because that breaks the recommended modularity of Meteor since 1.3.

Thoughts?

Edit: Better to show an example:

hwillson · April 22, 2016, 12:54pm

Both getText and getBinary work relative to the root /private directory only:

github.com

meteor/meteor/blob/310d6df4ac2b411425c626094ed3d378206fee18/tools/isobuild/bundler.js#L1582


 * @summary The namespace for Assets functions, lives in the bundler.
 * @namespace
 * @name Assets
 */
Assets: {


  /**
   * @summary Retrieve the contents of the static server asset as a UTF8-encoded string.
   * @locus Server
   * @memberOf Assets
   * @param {String} assetPath The path of the asset, relative to the application's `private` subdirectory.
   * @param {Function} [asyncCallback] Optional callback, which is called asynchronously with the error or result after the function is complete. If not provided, the function runs synchronously.
   */
  getText: function (assetPath, callback) {
    return getAsset(item.assets, assetPath, "utf8", callback);
  },


  /**
   * @summary Retrieve the contents of the static server asset as an [EJSON Binary](#ejson_new_binary).
   * @locus Server
   * @memberOf Assets

You could consider create a matching hierarchy in your /private subdirectory though, like:

/private
  /bunits
  /forecasts
    forecasts.graphql

This will at least help keep things somewhat organized.

batjko · April 22, 2016, 1:01pm

Yea, I was hoping to avoid that, since I wanted to keep each module as self-contained as possible.
But there we are.

Thanks for checking, @hwillson!