rave-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erin Noe-Payne <erin.noe.pa...@gmail.com>
Subject Re: Deprecating PageType
Date Tue, 18 Jun 2013 19:25:59 GMT
I'm trying to relate the endpoints to the queries. At the moment our
endpoint is:

If pagetype is a string, then /pages/{context} is a query from pages
where page.pageType={context}.
{Identifier} is a moving target. In the case of portal, I want pages
of type portal which are visible to userId. In the case of profile,
you want pages of type profile owned by userid (I think?).

If I add a new context like project portfolios, I will want the
identifier to correspond to a project's id or title. So how do we
implement the idea that a context has a subject?

On Mon, Jun 17, 2013 at 2:15 PM, Matt Franklin <m.ben.franklin@gmail.com> wrote:
> On Mon, Jun 17, 2013 at 2:12 PM, Erin Noe-Payne <erin.noe.payne@gmail.com>wrote:
>> How do you see context of pages being defined instead?
> The simplest approach is to change the pageType property of the page to be
> a string.  Alternative suggestions welcomed.
>> On Monday, June 17, 2013, Matt Franklin wrote:
>> > As we move to a more generic context (workspace) model for Rave, we will
>> > need to remove current constructs like the PageType enumeration.  This
>> > enumeration statically defines the types of pages that can be queried
>> from
>> > Rave.  A more appropriate model is to use the context name as the "page
>> > type" and allow that to be passed all the way through the stack.
>> >
>> > Assuming lazy consensus, I will commit code that deprecates the PageType
>> > enumeration in 0.22 before the end of the week.
>> >
>> > -Matt
>> >

View raw message