SkyeYoung commented on issue #1110:
URL: 
https://github.com/apache/apisix-website/issues/1110#issuecomment-1133826303

   IMO, It’s okay.
   
   获取 Outlook for iOS<https://aka.ms/o0ukef>
   ________________________________
   发件人: Barchiel ***@***.***>
   发送时间: Sunday, May 22, 2022 2:08:02 PM
   收件人: apache/apisix-website ***@***.***>
   抄送: Young ***@***.***>; Author ***@***.***>
   主题: Re: [apache/apisix-website] [Site][Discussion]: maintain a VSCode config 
dir (Issue #1110)
   
   
   @barchielAbyss<https://github.com/barchielAbyss> I accept this change and 
you can create a Proposal if needed.
   
   But I also want to point out that if we add it, then we need to make sure 
that the vscode configuration is maintained for a long time.
   
   In addition to this, I am very concerned that people will want to add 
configurations for various editors or IDEs such as Emacs, Vim, Neovim, 
Webstorm, etc.
   
   I have previously considered adding some of the recommended vscode plugins 
to the README, so if you want to do that, please maintain an additional 
document for newbies. (It is best to create a separate document and add a link 
to the README.)
   
   I don't think it's too much of a problem to maintain documentation, but they 
need to be found quickly, So which README should it be placed in? I think it is 
/README.md, what do you think? Wouldn't it be a bit strange, what was written 
there was a project introduction
   
   ―
   Reply to this email directly, view it on 
GitHub<https://github.com/apache/apisix-website/issues/1110#issuecomment-1133826012>,
 or 
unsubscribe<https://github.com/notifications/unsubscribe-auth/ALRIROBUNHSFKMA2M5CKHKLVLHFMFANCNFSM5WSZ3GUQ>.
   You are receiving this because you authored the thread.Message ID: 
***@***.***>
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to