Jon Pretty
Jon Pretty
We should be able to remove any unnecessary imports (those containing projects which aren't used for projects in the layer) and then replace imports of layers which define zero projects...
This introduces a very basic REST server for VS Code support. Clone this repository, then build and install Fury with ```sh make install ``` If Fury is already running stop...
Output on OSX revealed a stack trace: ``` java.util.concurrent.ExecutionException: org.eclipse.lsp4j.jsonrpc.ResponseErrorException: expected whitespace or eof got u (line 1, column 2316) at org.eclipse.lsp4j.jsonrpc.RemoteEndpoint.handleResponse(RemoteEndpoint.java:209) at org.eclipse.lsp4j.jsonrpc.RemoteEndpoint.consume(RemoteEndpoint.java:193) at org.eclipse.lsp4j.jsonrpc.json.StreamMessageProducer.handleMessage(StreamMessageProducer.java:192) at org.eclipse.lsp4j.jsonrpc.json.StreamMessageProducer.listen(StreamMessageProducer.java:94) at org.eclipse.lsp4j.jsonrpc.json.ConcurrentMessageProcessor.run(ConcurrentMessageProcessor.java:99)...
It seems like the best place to specify shading of a particular package would be at the layer import level. If you import a conflicting version of a particular project,...
There's currently no `update` command for layers, which means that in order to change a layer, for example, to select a different schema, it's necessary to delete the old one,...
We should add Fury to the ["Awesome IPFS" list](https://github.com/ipfs/awesome-ipfs).
This would be an enhancement to the `proliferate` command to allow one _version_ of a project to overwrite another version.
This is apparent, for example, when updating a layer using the new `export` menu. It appears like IPFS is called many times, possibly once for every layer in the tree....