Rethinking exclusion of alias from “all”
I asked a while back if Compass should include the alias within the all field or not. Here is the question and the decision was to remove it. After getting some emails and based on some recent forum posts, I am not sure that this is the best “out of the box” experience for Compass users. I am considering turning this back and currently leaning towards it. What do you say? I wish to nail this before 2.0 RC1.
April 3rd, 2008 at 8:21 am
I think this feature is useful in some circumstances, maybe it could be optional.
April 3rd, 2008 at 8:29 am
It is optional, and can be controlled using a flag. The question is what the flag default will be. To include or not to include (the alias), that is the question.
April 3rd, 2008 at 11:18 am
The best solution would be to make very clear statement about this topic in the documentation (probably with some nice examples). Then it really does not matter what is the default value. I can imagine that the turn-on/off really depends on the use case. For example with cook book application it is not that useful to return all ingredients as a response to ‘ingredient’ user query (assuming that each Receipt object will have some property of List) - thus it is OK to turn it off. However, with HR application it make sense to return list of all managers as a response to ‘manager’ user query. Just my 2 cents.