Naming conventions and specification infrastructure

[ardalis]

Naming conventions and specification infrastructure

[fiseni]

I gave a second thought to this. We will utilize a newly created builder which will encapsulate all the methods for creating the specification. So, the Query won't be this, but actually will return a instance of the builder.
I think this will offer much "cleaner" usage, since all the properties that have nothing to do with building the spec are not listed at all.

    public class BlogWithPostsSpec : BaseSpecification<Blog>
    {
        public BlogWithPostsSpec(int id) : base()
        {
            // Query contains only methods for building the spec, which are not available otherwise.
            Query.Where(x => x.Id == id)
                .Include(x => x.Posts)
                .EnableCache(nameof(BlogWithPostsSpec), id)
                .ApplyPaging(10, 20)
                .OrderBy(x => x.Name)
                .ThenByDescending(x => x.Url);
        }
    }

[ardalis]

I agree with using Builder pattern here.

[fiseni]

This issue is addressed with PR #30
If no one has comments, we may close it.