Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Gist sharing support #330

Merged
merged 11 commits into from
Jul 15, 2023
Merged

Add Gist sharing support #330

merged 11 commits into from
Jul 15, 2023

Conversation

corwin-of-amber
Copy link
Member

This is a merge of #328.

CHANGES.md Outdated
--------------

- Add support for saving and loading scratchpad snippets using Gist (@Eladkay)

# jsCoq 0.17.0
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually 0.17.0 was never released so this is going to be part of 0.17.0

description: 'jsCoq exported file',
'public': false,
files: {
'scratch.v': {
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note: we can probably use the filename from the editor if it exists (but for now scratch.v is fine).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can, but keep in mind that it doesn't matter for literally anything because we're just saving and loading

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the Flèche-based branch of jsCoq, there is a notion of workspace server-side, as LSP requires.

Indeed I wonder how to map the notion of "file(s) in a Coq workspace", (where the Coq workspace is just the set of visible .vo files for Require) to the Gist namespace.

But indeed didOpen LSP call requires an URI identifier for the document, so that can be IMHO assumed to exist on the client side.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can, but keep in mind that it doesn't matter for literally anything because we're just saving and loading

yes this would be just for posterity so that when you load you can also "know" what the original filename was.

@corwin-of-amber
Copy link
Member Author

Would close #311

@corwin-of-amber corwin-of-amber merged commit c23c302 into v8.17 Jul 15, 2023
3 checks passed
@ejgallego ejgallego deleted the v8.17+gist branch July 15, 2023 10:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants