question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Rename the repository to `zowe-explorer`

See original GitHub issue

The fact that our repository is called vscode-extension-for-zowe on github, but ZOWE Explorer elsewhere (marketplace, ZOWE docs) is somewhat confusing.

Could we consider renaming this repository to zowe/zowe-explorer?

Issue Analytics

  • State:open
  • Created 3 years ago
  • Reactions:3
  • Comments:10 (8 by maintainers)

github_iconTop GitHub Comments

5reactions
crawrcommented, Mar 24, 2021

Hi All,

As per our last discussion, it is our squad’s decision if we want to go ahead and change our repository name. The suggested new name would be zowe-explorer-vscode. We would like to call for a vote if we want to proceed with this change.

Before voting, here is a reminder of some of the implications brought up during the discussion:

  1. Documentation changes. There would be a huge amount of change in docs including zowe doc-site, zowe website, readMe files from existing extensions, blogs and other articles. GitHub might have mitigation for this in the form of link redirects for a short amount of time.
  2. We need to inform other squads and stakeholders about this change.
  3. Does the unique identifier also need to be changed in the future?

Please vote using the reactions below: ❤️ -> I agree with the change of repository name to zowe-explorer-vscode 😕 -> I have more questions, comments, concerns 👀 -> No change

3reactions
t1m0thyjcommented, Mar 15, 2021

I support the idea of renaming the repository 🙂 When I want to access the ZE GitHub repo, I often type “zowe explorer” in my address bar expecting the URL to appear from my browsing history, but it doesn’t because ZE isn’t the repo name.

Edit: Perhaps “vscode” should still be kept in the name (e.g., “zowe-explorer-vscode”), to avoid confusion with the other Zowe Explorer? This could also set a naming convention in case Zowe Explorer is ported to other platforms in the future (e.g., “zowe-explorer-intellij”).

Read more comments on GitHub >

github_iconTop Results From Across the Web

Visual Studio Code (VS Code) Extension for Zowe - Zowe Docs
The Zowe Explorer extension for Visual Studio Code (VS Code) ... Enables you to create, modify, rename, copy, and upload data sets directly ......
Read more >
Zowe Explorer - GitHub
Zowe Explorer repository includes several folders with files that let you build and configure various aspects of the extension. The bulk of the...
Read more >
Managing z/OS resources with IBM RSE API Plug-in for Zowe ...
This section describes the procedure of managing z/OS resources with the Zowe Explorer VS Code extension. To get set up with VS Code,...
Read more >
Known issues and limitations | IBM Z® Open Editor
The Zowe Explorer setting "zowe.security. ... Rename symbol in file and across the multiple files; Outline view; Code completion; Snippets ...
Read more >
@zowe/zowe-explorer-api - npm
Extensibility API for Zowe Explorer is a collection of APIs that can be used to extend the Zowe Explorer VS Code extension with...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found