Łukasz Jagodziński

No problem :) As I said I think the problem may be in load order, so use imports instead of globals. That's much more reliable.

Hmm right, now it's possible to redeclare ENUM which should not be possible. I will make a fix for that. Thanks for noticing it!

Hi. It's hard to tell what the problem is without reproduction repository. Please, create one that only tries replicate given problem. On Fri, Jul 6, 2018, 10:36 AM Alex Rubner...

Maybe I will consider adding something to the docs but it's quite obvious that you can't add `.` to the field name because you can't do either in MongoDB. Maybe...

@rub1e yep I know how it's done in `simple-schema`. Nested classes/models should be defined in a separate "object". Take a look at GraphQL. It is even more important when your...

It's only true for classes that have collection attached to it, so that's why you don't see this method.

No, I think documentation doesn't mention it. It would be great if you could make a PR and add proper info.

I can help you with that :) it's not difficult. There is the [`gh-pages`](https://github.com/jagi/meteor-astronomy/tree/gh-pages) branch in which you have all the documentation. In [this](https://github.com/jagi/meteor-astronomy/blob/gh-pages/_includes/v2/key_concepts/setting_and_getting_values.md) file you have a description of...

When you're creating issue on GH you should always create reproduction repository with just trimmed down version of your problem. Just the `PublishGame` method, publishedAt, isPublished and paramCounters fields.

It's not reproduction repository. You have to trim it down even more just to essentials to reproduce error