From 846a40ea10988d2cc2fae63a70e06be60813d7db Mon Sep 17 00:00:00 2001
From: Kunihiko Toumura <30313213+k-toumura@users.noreply.github.com>
Date: Fri, 18 Jan 2019 17:59:32 +0900
Subject: [PATCH] add comment for plugin architecture

---
 Design:-Flow-Linter.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/Design:-Flow-Linter.md b/Design:-Flow-Linter.md
index 3a213bb..8bf1b4b 100644
--- a/Design:-Flow-Linter.md
+++ b/Design:-Flow-Linter.md
@@ -68,6 +68,8 @@ module.exports = {
 - Flow-check code in plug-in is used on both CLI (runs on node.js) and Editor (runs on browser).  To use same code in both node.js and browser, there are tools for generate codes for both:
   - [Browserify](http://browserify.org/): get all dependent npm modules and put in one script file.
   - [Babel](https://babeljs.io/): convert modern JavaScript (ES2015+) code to (traditional) JavaScript code that can be executed on various browsers.
+- [Language Server Protocol](https://microsoft.github.io/language-server-protocol/) defines the protocol used between an editor and a language server that provides language features like lint.  It may be alternative option to implement lint function as a language server embedded in a Node-RED server.
+  - Language Server Protocol itself is aimed for line-oriented text programming languages.  It is not suitable for visual programming language like Node-RED.  If we adopt the LSP, We might incorporate only their 'Client-Server' architecture, and not incorporate their protocol or data model.
 
 ## Configuration
 Linter reads configuration files in following order: