Feature Proposal: Add a context that represents the core feature level of Foswiki

Motivation

We have the API version that can be checked for changes to Func, Meta and other core API implementations, but other changes to rendering, scripts, etc. Don't really fall into the API category. It would be nice if skins and other extensions could have a context to test to determine the core feature set.

Templates have a simple context test as part of the TMPL:P macro, but can't easily do more complex comparisons.

For the new indent syntax, CrawfordCurrie added a new context: SUPPORTS_PARA_INDENT, it would be nice if this was generalized.

Description and Documentation

The context would be FeatureLevel[Major][Minor](patch)With the patch level being omitted unless required.

Add the following contexts:

FeatureLevel10
Represents the 1.0.x release stream. (Historical consistency only, not really needed)
FeatureLevel11
The 1.1.x release stream.
FeatureLevel12
Upcoming 1.2.x release.

Examples

Impact

%WHATDOESITAFFECT%
edit

Implementation

-- Contributors: GeorgeClark - 05 Aug 2012

Discussion

Does this mean we will have FeatureLevel11 as well as FeatureLevel116 at the same time?

-- MichaelDaum - 05 Aug 2012

I think that would be the simplest, to add to the contexts, not replace them. Also, I would hope that we don't need one for every patch release, only releases where features are added that would impact skin or plugin operation. If the Release Manager is doing a reasonable job, the dot releases should not be picking up features. smile

-- GeorgeClark - 05 Aug 2012

Changing this to accepted.

-- GeorgeClark - 09 Oct 2012

Moved this to 1.2. No real need for 1.1.6, and it probably could stand to be reviewed - is this generic feature level the way to go, or feature specific contexts, like CDot had added.

-- GeorgeClark - 22 Oct 2012

Parking this proposal. No overriding need has come forward.

-- GeorgeClark - 01 Apr 2014
 
Topic revision: r9 - 19 Nov 2015, GeorgeClark - This page was cached on 13 May 2020 - 22:23.

The copyright of the content on this website is held by the contributing authors, except where stated elsewhere. See Copyright Statement. Creative Commons License    Legal Imprint    Privacy Policy