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

[FEATURE]: add information about updating jayvee extension in the docs #480

Merged

Conversation

OmarFourati
Copy link
Collaborator

@OmarFourati OmarFourati commented Dec 10, 2023

Description:

Updating jayvee through npm wasn't enough to have it fully functionning in VS Code. An update of the extension has to be done as well. This information was not present anywhere.

Solution

Add this information to the "update" part of the jayvee introduction

Related to #477.

@OmarFourati OmarFourati requested a review from rhazn December 10, 2023 16:46
Copy link
Contributor

@rhazn rhazn left a comment

Choose a reason for hiding this comment

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

Left some high level feedback for the into.md file directly.

@@ -23,6 +24,10 @@ npm install -g @jvalue/[email protected]

Updating the interpreter is done by reinstalling it using `npm`. Make sure to also update the [VSCode plugin](#vscode-plugin) to match the installed interpreter if you use it.

IMPORTANT: If a new Jayvee update is available, you need to update your Jayvee extension as well.
Copy link
Contributor

Choose a reason for hiding this comment

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

"Your VSCode extension for Jayvee" would be the correct wording.

@@ -23,6 +24,10 @@ npm install -g @jvalue/[email protected]

Updating the interpreter is done by reinstalling it using `npm`. Make sure to also update the [VSCode plugin](#vscode-plugin) to match the installed interpreter if you use it.

IMPORTANT: If a new Jayvee update is available, you need to update your Jayvee extension as well.

Extensions and updates can be found [here](https://github.com/jvalue/jayvee/releases/tag/v0.2.0-alpha).
Copy link
Contributor

Choose a reason for hiding this comment

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

Should link to https://github.com/jvalue/jayvee/releases/latest, not to a specific version.

Copy link
Contributor

Choose a reason for hiding this comment

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

Overall it would be good to add a completely new document (e.g., update.md) that we can link to. That document should include only a documentation on how to update to a new Jayvee version:

  • That you need to update Jayvee and the VSCode extension both
  • The explicit npm install command for that version
  • How to update the VSCode extension
  • How to verify that you have the right jayvee version installed
  • How to verify that you have the right VSCode extension installed

You can then link that new document from here.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I created the update.md file and logic.
How can I now link this page without having it in the header or on the menu at the left side ? Couldn't find any example of such a situation.

Copy link
Contributor

Choose a reason for hiding this comment

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

Not sure actually. We use https://docusaurus.io/ so maybe they have something in their docs? I assume it has something to do with the markdown frontmatter / metadata between the dashes, e.g. for intro.md

---
sidebar_position: 1
---

I assume there is some boolean there that hides it from the menu?

Once you have updated the PR so the comments are fixed, you can retrigger the review by the way, then I can have another look :).

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I was not able to find a solution to not have it in the sidebar.
Solutions ? Leave it right under introduction to Jayvee ?

Another option would be a menu point under : Introduction of Jayvee.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I Updated the docs in a way that i think is the best within implementing the update page:
image

Getting started (which is actually the wording I found on 80% of documentations) = the intro page
Update Javee: Information about updating Javee

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@rhazn need review on this to resolve the conversation and ask for an overall review of the PR.

Copy link
Contributor

Choose a reason for hiding this comment

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

If you need a review, please re-request a review (top right). But make sure the CI works beforehand, right now it is failing.

@OmarFourati OmarFourati force-pushed the feature/update-docs-for-jayvee-updating branch from 4649d90 to d341ba5 Compare December 26, 2023 09:11
@OmarFourati OmarFourati requested a review from rhazn December 26, 2023 10:05
Copy link
Contributor

@rhazn rhazn left a comment

Choose a reason for hiding this comment

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

I think this is well done (after accepting my suggestions/some proofreading ;)). I like the Getting Started wording and I am okay with the category in the docs.

Because it is a larger navigation change I'd run it by @georg-schwarz as well though, would you mind having a look the the screenshot Omar posted? Is that setup okay for you?

"position": 1,
"link": {
"type": "generated-index",
"description": "All the essentials Information to get started with Javee."
Copy link
Contributor

Choose a reason for hiding this comment

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

Please proofread these texts a bit ;).

Suggested change
"description": "All the essentials Information to get started with Javee."
"description": "All the essential information to get started with Jayvee."


# How to update Jayvee

Jayvee is constently getting updates as a dedicated team of developers diligently addresses performance issues and incorporates new features to meet the evolving needs of its user base.
Copy link
Contributor

Choose a reason for hiding this comment

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

Same here, some proofreading or automated help (I suggest languagetool). Also no need for marketing texts here ;).

Suggested change
Jayvee is constently getting updates as a dedicated team of developers diligently addresses performance issues and incorporates new features to meet the evolving needs of its user base.
Jayvee is consistently getting updates. To ensure you use the most recent version, please regularly update the interpreter and VSCode extension.


- Then, download the latest `jayvee.vsix` file.

- Finally, open your Command Prompt(terminal), and paste the code below:
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
- Finally, open your Command Prompt(terminal), and paste the code below:
- Finally, to install the extension using the CLI, paste the code below into your command line:

code --install-extension jayvee.vsix
```

For manual installation, follow this [link](https://code.visualstudio.com/docs/editor/extension-marketplace#_install-from-a-vsix) for the official VSCode documentation.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
For manual installation, follow this [link](https://code.visualstudio.com/docs/editor/extension-marketplace#_install-from-a-vsix) for the official VSCode documentation.
If you'd rather use the manual installation, follow this [link](https://code.visualstudio.com/docs/editor/extension-marketplace#_install-from-a-vsix) for the official VSCode documentation.


### Version Check

To verify wether the wanted version of Jayvee and VSCode extension where installed successfully, you can run in your Command Prompt(terminal):
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
To verify wether the wanted version of Jayvee and VSCode extension where installed successfully, you can run in your Command Prompt(terminal):
To verify wether the wanted version of Jayvee and VSCode extension where installed successfully, you can run in your command line:


For the **VSCode extension**:

In VSCode: Go to the extensions menu, and look for `Jayvee`. The version is then displayed on the information page of the extension.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
In VSCode: Go to the extensions menu, and look for `Jayvee`. The version is then displayed on the information page of the extension.
Go to the extensions menu, and look for `Jayvee`. The version is then displayed on the information page of the extension.

Comment on lines 28 to 36
Updating the interpreter is done by reinstalling it using `npm`. Make sure to also update the [VSCode plugin](#vscode-plugin) to match the installed interpreter if you use it.

IMPORTANT: If a new Jayvee update is available, you need to update your VSCode extension for Jayvee as well.

More details on updating can be found [here](./update.md).

```bash
npm install -g @jvalue/jayvee-interpreter
```
Copy link
Contributor

Choose a reason for hiding this comment

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

The point of this was to move all the update docs to one place, not keep it around in two places. So here, please just link to the update page and remove the rest. E.g.

Suggested change
Updating the interpreter is done by reinstalling it using `npm`. Make sure to also update the [VSCode plugin](#vscode-plugin) to match the installed interpreter if you use it.
IMPORTANT: If a new Jayvee update is available, you need to update your VSCode extension for Jayvee as well.
More details on updating can be found [here](./update.md).
```bash
npm install -g @jvalue/jayvee-interpreter
```
Details about how to update Jayvee and the VSCode extension can be found [here](./update.md).

@OmarFourati
Copy link
Collaborator Author

I think this is well done (after accepting my suggestions/some proofreading ;)). I like the Getting Started wording and I am okay with the category in the docs.

Because it is a larger navigation change I'd run it by @georg-schwarz as well though, would you mind having a look the the screenshot Omar posted? Is that setup okay for you?

Tagged @georg-schwarz for a review as well.

Copy link
Member

@georg-schwarz georg-schwarz left a comment

Choose a reason for hiding this comment

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

LGTM.

Before merging, please make sure the routing from the landing page still leads to the intro doc and not the generated index.

It might require a change in the docusaurus config file.

Copy link
Contributor

@rhazn rhazn left a comment

Choose a reason for hiding this comment

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

Nice, well done. Please pay a bit more attention to grammatical and typing mistakes going forward though, especially when writing documentation.

@rhazn
Copy link
Contributor

rhazn commented Dec 28, 2023

Ah, I note this branch has conflicts with the main branch. You'll need to rebase it on main (or merge main into this) before we can merge @OmarFourati

@OmarFourati
Copy link
Collaborator Author

Should be now updated and main is merged.

@OmarFourati OmarFourati requested a review from rhazn January 22, 2024 15:16
Copy link
Contributor

@rhazn rhazn left a comment

Choose a reason for hiding this comment

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

Looks good, one last update hopefully :D.

@@ -83,7 +80,7 @@ jv <file> -d --debug-granularity peek --debug-target MyExtractorBlock,MySinkBloc

## Examples

You can find multiple examples with inline explanations [here](./examples/README.mdx).
You can find multiple examples [here](https://github.com/jvalue/jayvee/tree/main/example). Copy them to your local file system and execute them with the `jv` command on your command line (see [usage](#usage)).
Copy link
Contributor

Choose a reason for hiding this comment

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

I think this should be reverted/combined again, we decided to link to the examples in the docs, not on github.

Suggested change
You can find multiple examples [here](https://github.com/jvalue/jayvee/tree/main/example). Copy them to your local file system and execute them with the `jv` command on your command line (see [usage](#usage)).
You can find multiple examples with inline explanations [here](./examples/README.mdx). You can copy them to your local file system and execute them with the `jv` command on your command line (see [usage](#usage)).

@OmarFourati OmarFourati requested a review from rhazn January 24, 2024 15:06
@rhazn
Copy link
Contributor

rhazn commented Jan 25, 2024

Nice, thank you. I'll merge this very soon after next weeks MADE lecture just to make sure no change happens with the docs until then :).

@rhazn rhazn merged commit 14ea9c3 into jvalue:main Feb 1, 2024
3 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Feb 1, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants