Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disable Client Class Creation #39

Closed
davidruisinger opened this issue Jan 29, 2016 · 9 comments
Closed

Disable Client Class Creation #39

davidruisinger opened this issue Jan 29, 2016 · 9 comments

Comments

@davidruisinger
Copy link

I'm aware that this it not a big security risk but I just don't want my DB to get spammed with data that I don't need.

@davidaik
Copy link

👍 Was thinking of posting the same thing

@NorthMcCormick
Copy link

+1

1 similar comment
@andrewoons
Copy link

+1

@5amfung
Copy link

5amfung commented Jan 29, 2016

There should be a setting to control either of this or #26.

@gfosco
Copy link
Contributor

gfosco commented Jan 29, 2016

Agreed, we should add this option.

@gfosco
Copy link
Contributor

gfosco commented Jan 31, 2016

Less simple than expected. The Schema class is what creates a new collection, but it isn't passed any of the configuration to hold an option like this. Still working on a method for this.

@Morbix
Copy link

Morbix commented Jan 31, 2016

+1

@lucianmat
Copy link

Have worked on this issue, proposed solution will freeze schema (classes and fields) unless NODE_ENV === 'development' or masterkey is used.
Have submited a PR ... :)

@drew-gross
Copy link
Contributor

Added in #684

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants