v-lafeychine (329a47e3) at 04 Feb 14:46
Initial commit
v-lafeychine (5f2bfab8) at 29 Jan 18:03
Initial commit
v-lafeychine (f66ffc71) at 29 Jan 13:43
Initial commit
v-lafeychine (b2c6fc21) at 27 Jan 23:57
Initial commit
v-lafeychine (d2db3855) at 27 Jan 23:26
Initial commit
v-lafeychine (66a8c893) at 25 Jan 16:35
Initial commit
The following code is accepted but shouldn't:
» def foo := Prop
✓
» def foo.{} := Prop
✓
v-lafeychine (202ac1e5) at 11 Jan 20:32
Resolve "Bug(Parser): no error when defining a declaration with the...
Closes #81
Closes #81
This would definitely be an integration test.
We should really add such infrastructure to prevent other bugs.
In the meantime, since this issue is flagged as a bug, we can merge.
tbh, I would prefer to have proost
as an IDE plugin.
We gave a name to:
tilleul
);madelaine
) and;proost
)Technically, the extension should be proost
that includes:
madelaine
tilleul
server.Please feel free to share your suggestions (@loutr).
See #113
By default, RUST_BACKTRACE
should always be enabled in tilleul
.
Every LSP client should have a clear explanation why the server crashed.
block-spacing
seems not to be in conflict, can you add it back?
Be careful with the if-return-else
code smell.
if (givenPath === undefined) {
throw new Error("`proost-lsp.serverPath` is illed-formed");
}
const result = spawnSync(givenPath);
if (result.status === SUCESS_STATUS) {
return givenPath;
}
[...]
This is awkward if this client is named Proost LSP, it's even more awkward when reading this line:
This extension uses
tilleul
as default backend, but any proost LSP can work.
I suggest this:
# Madelaine extension for Visual Studio Code
This is an extension for Proost, including a syntactic coloration along with an LSP client for `tilleul`.
```bash
$ npm install
$ npm run compile
The current implementation of the LanguageServer
trait for Tilleul
define the capabilities as
ServerCapabilities {
definition_provider: Some(OneOf::Left(true)),
text_document_sync: Some(TextDocumentSyncCapability::Kind(TextDocumentSyncKind::FULL)),
..ServerCapabilities::default()
}
while tilleul does not currently provide an handle for definition requests or synchronization.