The public folder and exporting schemas without collections.

[nayelo]

How should we import/export collections which have schemas attached and sub-schemas that are used over multiple collections? I have tried to retain a convention of exporting from a lib/collections.js file, but my sub-schemas (meta and admin) are not being imported as they are not attached to a collection. If I define the Meta sub-schema in the schemas/Constellations.js file the error disappears, but that is not a real solution as the sub-schemas are used across many collections.

Throwing Meta is required from (server/configs/initial_adds.js:18:22) in the attached files.

I also have svg files in the public folder that I need to access in the client components. Is there a Mantra standard for either case?

https://github.com/GetGee/G/tree/master/lib
https://github.com/GetGee/G/tree/master/server

[martinwh99]

i'm also using SimpleSchema with sub-schemas in Mantra. My collections.js looks like this and it works:

import Employees from './schemas/Employee';
import Tenants from './schemas/organisations/Tenants';
import Organisations from './schemas/organisations/Organisations';
import BaseRoles from './schemas/authorizations/BaseRoles';
import Groups from './schemas/authorizations/Groups';

export {

Employees,
Tenants,
Organisations,
BaseRoles,
Groups

}

in containers folder you can than use

....
const {LocalState, Meteor, Collections} = context();
...
const employee = Collections.Employees.findOne(selector);