From 234aa2664db4fa153515cc35293ae5b65f4ac6a8 Mon Sep 17 00:00:00 2001
From: Kunihiko Toumura <30313213+k-toumura@users.noreply.github.com>
Date: Fri, 18 Jan 2019 18:04:19 +0900
Subject: [PATCH] Updated Design: Flow Linter (markdown)

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

diff --git a/Design:-Flow-Linter.md b/Design:-Flow-Linter.md
index 8bf1b4b..4b4122d 100644
--- a/Design:-Flow-Linter.md
+++ b/Design:-Flow-Linter.md
@@ -70,6 +70,7 @@ module.exports = {
   - [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.
+  - If we adopt this architecture, the linter need not to generate code for server and browser.  But we have to estimate an overhead to send flow object from browser to server.
 
 ## Configuration
 Linter reads configuration files in following order: