Hi,
On Mon, Oct 6, 2014 at 10:06 AM, Shiroshica Kulatilake <sh...@wso2.com> wrote: > Hi, > > So - what is the guarantee that when something changes the relevant JSON > file will also be changed ? > Yes. This can be a problem. Because some of the configurations can be different among the IaaS such as zone and region. > > I am totally +1 for having these files plus including them in > documentation - however - not sure whether we will tend to not update these > again. > Yes. Having the common JSON files against the release. Already we have that in the wiki. > > So - how about having this in some format which breaks if the correct JSON > file is not there and the easiest example I can think of is tests. > > For starters can we have a simple script which would invoke all the REST > APIs using sample JSON files and add this to the build ? > +1 for add this to build. > > > WDYT ? > > Thank you, > Shiro > > > > On Mon, Oct 6, 2014 at 7:49 AM, Udara Liyanage <ud...@wso2.com> wrote: > >> >> +1 for the idea. Only basic samples are available in docs. >> Shall we have a sample directory in root level where it is easy to find , >> users might not search for samples in tools directory. >> >> >> Touched, not typed. Erroneous words are a feature, not a typo. >> > > > > -- > Shiroshica Kulatilake > > Architect, > WSO2, Inc. http://wso2.com/ > Phone: +94 776523867 > -- Regards, Manula Chathurika Thantriwatte Software Engineer WSO2 Inc. : http://wso2.com lean . enterprise . middleware email : manu...@wso2.com / man...@apache.org phone : +94 772492511 blog : http://manulachathurika.blogspot.com/
