This Editor is basically an IDE for APIs. I don't think documentation fits in there. Users can of course edit the Swagger docs, which is kind of similar to writing Java docs. But I don't think we should be allowing people to update .doc, .pdf, etc type of docs using this editor. Its not standard practice we follow when writing usual code.
With regard to importing and collaborating, I think they're two different aspects. Importing basically means you "download" something from a known server. Collaborating simply means doing a git pull. When writing Java code, we usually git pull and start editing, we don't "import" code as such. So I don't see "import" as a critical part to have , at least in the first iteration. I think its important to think of this editor like a standard IDE. If we're doing something on this editor that we don't usually do on a standard IDE, then we need to think twice to see if its really necessary. Since this is a completely new component to the product, I think we should keep things as simple as possible and focus on the most critical parts to get the job done. We can of course keep adding stuff on demand, if users require them. On Wed, May 17, 2017 at 5:28 PM, Tharika Madurapperuma <[email protected]> wrote: > Hi Chamin, > > On Wed, May 17, 2017 at 12:29 PM, Chamin Dias <[email protected]> wrote: > >> Since this is a subset of API Publisher, it would be better to list down >> and finalize the features of API Editor which are going to be inherited >> from Publisher. The reason is, it will help us to come up with an effective >> implementation mechanism (like reusing existing functions etc.). WDYT? > > > As of now the following are the main features inherited by the API Editor > from the API Publisher, > > - Creating an API > - With endpoints > - By importing a swagger definition > - As a Mock API > - Specifying API resources > - API level endpoints > - Mediation > - Scripting > - API Import Export > > API Editor can have its own functionalities which are not in the API > Publisher such as, > > - API Console for testing the API > > Will keep the list updated with any changes. > Thanks, > Tharika. > > -- > *Tharika Madurapperuma* > Software Engineer | WSO2, Inc. > > Email : [email protected] > Mobile : +94777875624 <+94%2077%20787%205624> > Web : http://wso2.com > > <http://wso2.com/signature> > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Nuwan Dias Software Architect - WSO2, Inc. http://wso2.com email : [email protected] Phone : +94 777 775 729
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
