strigo / vscode-linear-extension Goto Github PK

The extension doesn't yet have any functional tests. We need to add at least one base "happy path" test per utility function.

The extension communication can be more informative by adding context details to the status tray.

Here:

Extension's documentation is lacking some "do this to get that" instructions. Preferably with gifs.

If user doesnt restart vscode there is a bug "title cannot be empty" or something when creating an issue

As per https://code.visualstudio.com/api/references/extension-guidelines

The extension docs do not encourage users to report found issues. We need to add a section to the docs on what to do if a bug was found or if the user had some ideas to share.

The extension shows a progress for long lasting processes (e.g. "Fetch my issues") but the loader only shows "0%" and then "100%". It would be more indicative to change this percentage based on the real progress or at least on the expected progress.

The idea of the command is to allow to easily choose the next item to work on. This makes it kinda redundant. We should probably filter by status.

client.viewer.assignedIssues() allows to pass a filter: IssueFilter property, which in turn allows to pass a state: WorkflowStateFilter property. We can use that.

We have now 0.0.3 released but the Changelog doesn't have any description on what is there yet.

With this, users shouldn't have to hard-code API keys. VSCode should be able to get an access token using OAuth instead.

https://linear.app/integrations/vs-code
https://marketplace.visualstudio.com/items?itemName=Linear.linear-connect

Some of the data we retrieve when e.g. creating issues shouldn't change that often. We should cache this data so that the user doesn't have to wait for Linear to return it. For example, every time an issue is created, we re-retrieve the available workflow states and assignees. Those probably don't change very often, so we may as well retrieve them just once, save them to the global context when any command that uses them first runs, and use them instead of re-retrieving.

For now, this can be done for:

• Workflow states
• List of assignees (team members)
• My teams
• Available priorities

This can be a great addition to the extension, being able to select some code and comment with the selection on the issue in context.