Comments (5)
I understand the use case. Virtual fields are inherently "a collection2 thing" since they rely on transform, but it's possible that we could rethink the options "API" such that they are defined in SS definitions (similar to how denyUpdate
, etc. are inherently related to collections, but C2 has you define them in the schema definition object.
Specifically, I'm thinking of something like this:
var c = new Meteor.Collection("c", {
schema: new SimpleSchema({
creatorEmail: {
type: String,
virtual: function (doc) {
return getCreatorEmail(doc.createdBy);
}
}
});
});
This would require a way to tell the simple-schema package to ignore definitions that are virtual. I'm not sure I'm sold on doing it yet, but we can keep this open as a proposal.
from meteor-simple-schema.
You're right, it would also contextually make sense to keep it in c2.
As I am progressing on my first "rather complicated" meteor app (coming
from javaee), I see this multiple times. It may not always be the case
but for the current app, my schemas often share properties that can
otherwise be reused and be represented in other ways. Virtualfields
would have been a great fit for the use case. Currently, I'm trying to
pass those properties through some common utility functions after I
retrieve them. Trying to keep them reactive, though is the harder part
which seems to require even further abstraction. In the end, the code
becomes harder to follow and maintain.
On 01/16/2014 08:07 PM, Eric Dobbertin wrote:
I understand the use case. Virtual fields are inherently "a
collection2 thing" since they rely on transform, but it's possible
that we could rethink the options "API" such that they are defined in
SS definitions (similar to how |denyUpdate|, etc. are inherently
related to collections, but C2 has you define them in the schema
definition object.Specifically, I'm thinking of something like this:
var c = new Meteor.Collection("c", {
schema: new SimpleSchema({
creatorEmail: {
type: String,
virtual: function (doc) {
return getCreatorEmail(doc.createdBy);
}
}
});
});This would require a way to tell the simple-schema package to ignore
definitions that are virtual. I'm not sure I'm sold on doing it yet,
but we can keep this open as a proposal.—
Reply to this email directly or view it on GitHub
#49 (comment).
from meteor-simple-schema.
Oh, now I get this. Brilliant!
On 01/16/2014 08:07 PM, Eric Dobbertin wrote:
I understand the use case. Virtual fields are inherently "a
collection2 thing" since they rely on transform, but it's possible
that we could rethink the options "API" such that they are defined in
SS definitions (similar to how |denyUpdate|, etc. are inherently
related to collections, but C2 has you define them in the schema
definition object.Specifically, I'm thinking of something like this:
var c = new Meteor.Collection("c", {
schema: new SimpleSchema({
creatorEmail: {
type: String,
virtual: function (doc) {
return getCreatorEmail(doc.createdBy);
}
}
});
});This would require a way to tell the simple-schema package to ignore
definitions that are virtual. I'm not sure I'm sold on doing it yet,
but we can keep this open as a proposal.—
Reply to this email directly or view it on GitHub
#49 (comment).
from meteor-simple-schema.
@serkandurusoy, after checking out the code for the collection-helpers package, I'm thinking about deprecating virtual field support entirely and having people use that package instead. I think it's a better method. I also opened an issue for a collection-helpers enhancement which, if added, would I think meet your needs.
from meteor-simple-schema.
Sounds very logical and I'm sure everyone would benefit from the gains introduced by such decision.
from meteor-simple-schema.
Related Issues (20)
- AutoValue Doesn't Run On Server HOT 1
- [solved] custom function validation error HOT 1
- autoValue: calling fields() and siblingFields() yields no results on insert HOT 2
- Overwriting SimpleSchema regEx messages HOT 5
- Error: Invalid definition for inMenu field HOT 1
- Match.Where being instantiated as a class, causes error on Meteor 1.6.1 boot HOT 5
- Make a field conditionally required bug HOT 1
- Explicitly indicate this repo is deprecated HOT 1
- How to define a Custom Validation Error in Autoform >= 6.0 HOT 1
- Removing old field from old users? Ignore schema when using $unset ? HOT 1
- typo in dependencies in version 3.0.0 HOT 1
- 1.6.2 Has removed Deps from Tracker package HOT 4
- Warn / strip global regEx schemas? HOT 1
- the optional: true afFieldInput have the required attribute with it HOT 1
- error in Documentation [max] > {{max}} HOT 1
- "must be an object" error even though typeof() returns Object HOT 3
- $pull not behaving as expected HOT 1
- Move this package to Community Packages to support simpl-schema >=3.x HOT 1
- Update autoValue to accept async function HOT 2
- Typescript error when importing SimpleSchema HOT 6
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from meteor-simple-schema.