Hi, Nick has said sometimes that he doesn't see much feedback on the Projects feature.
I do like to use Projects. In my case for making test flows easily available for sharing with colleagues and using them in different test systems (VMs with different Windows versions, different Node versions using Docker). We're not seasoned developers using pull requests and reviews etc, so the simple options inside the editor are mostly OK.
There are some things that could be better, or different:
- Sometimes I the flow json marked as changed locally, but when I try to compare with previous commit no changes are shown when I click the file and it shows the two versions side by side. I think this happens when the order of items inside an object has changed, but the values have not changed. Easier to reproduce: only move a node, deploy, than undo and deploy.
- When I pull in changes made on another system, I get the notification that the flows on the server have been changed, and I can review the changes. When I do that review it says 'no merge conflicts', and I can click 'Merge'. But I can't actually see what the changes are in that view.
- When a larger data file (say a few MBs) gets added to the project, and I try to view that commit by clicking it in the commit history list, it can take a very long time for the list to render. I have to tell the browser I want to really wait a few times. Then all the data files added are shown expanded by default. It might be useful to show a collapsed view when multiple files are changed, and/or when there's a big file. And maybe limit the number of rows initially when expanding, like the behavior in github or bitbucket when dealing with larger files.
