👋 Possible dates/times:

• 3rd of April, Monday, 07:00 pm

Version Number

Ziya: 1.1.8
Node: 6.9.4
npm: 3.10.10
OS: Windows 10 (1607)
Browser: Mozilla Firefox 50.1.0

Test Case

Saving changes in a file

Steps to Reproduce

1. Open a text file from file tree.
2. Make some changes.
3. Press CTRL+S to save.
4. Check the file contents.

Expected Behavior

The changes must be visible in the file

Actual Behavior

The file is not changed and it is in original state.

Hi @altayaydemir. This can be our dev configuration issue. 👍

Hi @hwclass! 👯

I've took a general look at the project and I think it'd be a useful tool for developers. I decided to gather my questions under this issue so we'd have an archive about these discussions.

• I guess we are going to implement browsing through filesystem feature. I am not experienced with these kind of fs things. Do you recommend any resource so I can dig into it? (by the way, we can create or use a component like this for this feature.)
• Are we going to implement a code editor (and also a rich text editor other than native contentEditable feature, I guess React doesn't like it much)? (btw I have some experience with Codemirror and react-rte)
• If we are, how will be the decision process of types of editors we'll be using for various file types?
• Are we going to show hidden files/folders? 😅
• I'd be very happy to contribute this project, especially on the unit testing part 😈

We can discuss the roadmap and features we want to have on the first iteration under this issue or Telegram.

This functionality will have 2 options:

1 - With Ctrl + S shortcut (phase 1)
2 - Autosave mode (by codemirror) (phase 2)

1.1.9

Code Example

• Before committing changes, enter the following line:

git cz

Expected behavior

Some kind of "questionare" appears and asks for the details of the commit

Actual Behavior

git commit

And the usual "style" of committing to the project.

Hi @altayaydemir

Do you think that it would be nice to embed codemirror editor with this component? If so, this night I will be implementing this.

Regards

Baris

It is useful to add those kind of badges into readme files within github repos. I investigated and found two services:

shields.io
badges

We can build or use something like react-notification-system.

use that method: process.cwd()

Version Number

1.1.8

Test Case

Installing and running on Windows 10 (built 1607) with node v0.12.2 and npm v2.7.4

Steps to Reproduce

1. Used following command to install
   C:\> npm install ziya
2. In command prompt, type the app name to run
   C:\>ziya

Expected Behavior

Expected to run on Windows 10

Actual Behavior

Crashes with the error displayed below, without further information about a solution or workaround.

C:\Users[removed_for_privacy]\AppData\Roaming\npm\node_modules\ziya\src\server\index.js:25
app.get('/files/:path', (req, res) => {
^^
SyntaxError: Unexpected token =>
at exports.runInThisContext (vm.js:73:16)
at Module._compile (module.js:443:25)
at Object.Module._extensions..js (module.js:478:10)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)
at Function.Module.runMain (module.js:501:10)
at startup (node.js:129:16)
at node.js:814:3

Here we need the following:

• A subtitle of the application
• An animated gif showing the usage
• Installation and usage steps
• Contributors list
• Licence notice

We do not have a logo to be used as icon :(

Something like these blue dots:

Maybe going public means that we need to get more attention for future contributors also by the appearance of this application. I have some recommendations to implement:

Material UI
Material UI Light
Grommet
Elemental UI
Ant Design - has tree menu option
React Toolbox

We just should also keep the theme can be selectable in the further phases as well.

Btw we can put this issue for the next phases, maybe.