Skip to content

[ZEPPELIN-6255] added message in the create-repository-modal for user not to be confused.#5011

Merged
jongyoul merged 3 commits into
apache:masterfrom
yunajoe:feature/6255
Aug 15, 2025
Merged

[ZEPPELIN-6255] added message in the create-repository-modal for user not to be confused.#5011
jongyoul merged 3 commits into
apache:masterfrom
yunajoe:feature/6255

Conversation

@yunajoe

@yunajoe yunajoe commented Aug 4, 2025

Copy link
Copy Markdown
Contributor

…g a repository with an existing ID will update the existing repository

What is this PR for?

A few sentences describing the overall goals of the pull request's commits.
First time? Check out the contributing guide - https://zeppelin.apache.org/contribution/contributions.html

  • Currently, users can update the configuration of a registered repository used for dependency resolution by creating a new entry with the same ID under Add New Repository, but with different settings.

However, this behavior is not intuitive, and users may not realize that modifying an existing repository is possible in this way.

To improve clarity, we’ve added a simple explanation to the Interpreter page UI, informing users that creating a repository with an existing ID will update the existing configuration rather than creating a new one.

Alternatively, in the future, it may be worth considering implementing a dedicated Edit Repository feature, along with an option to Remove Repository, to make this workflow even clearer.

What type of PR is it?

Bug Fix
Improvement
Feature
Documentation
Hot Fix
Refactoring
Please leave your type of PR only

  • Improvement

Todos

  • - Task

What is the Jira issue?

How should this be tested?

  • Strongly recommended: add automated unit tests for any new or changed behavior
  • Outline any manual steps to test the PR here.

Screenshots (if appropriate)

image

Questions:

  • Does the license files need to update?
  • Is there breaking changes for older versions?
  • Does this needs documentation?

yunajoe added 2 commits August 4, 2025 23:08
…g a repository with an existing ID will update the existing repository

@hyunw9 hyunw9 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Could you please refine the PR description to make it easier for the reviewer to understand the changes?

Comment thread zeppelin-web-angular/.gitignore Outdated
.env
yarn.lock No newline at end of file
yarn.lock
.env.local No newline at end of file

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

i think you intended this not to upload this .env.local file, but it was uploaded. could you fix it ?

Comment thread zeppelin-web-angular/.env.local Outdated

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Please remove this configuration file.


function httpUrlToWSUrl(url) {
return url.replace(/(http)(s)?\:\/\//, "ws$2://");
return url.replace(/(http)(s)?\:\/\//, 'ws$2://');

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Is it by Linter?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

yes, would it be a problem?

@yunajoe yunajoe requested review from hyunw9 and jongyoul August 6, 2025 10:30

@jongyoul jongyoul left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM

@jongyoul jongyoul merged commit eb2e03e into apache:master Aug 15, 2025
16 of 18 checks passed
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.

3 participants