Skip to content

Set raw component url value when updating a component - #84

Merged
ivan-risueno merged 2 commits into
masterfrom
bugfix/component_url-not-getting-stored-anymore
Sep 4, 2026
Merged

ivan-risueno merged 2 commits into
masterfrom
bugfix/component_url-not-getting-stored-anymore

Conversation

@ivan-risueno

Copy link
Copy Markdown
Contributor

No description provided.


assertThat(result.getStatus()).isEqualTo(Status.CREATED);
assertThat(result.getComponentUrl()).isEqualTo("oldUrl"); // unchanged
assertThat(result.getComponentUrl()).isEqualTo(null);

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.

Ideally, we should never set null value to componentUrl, that's a bug we fixed in the recent past

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.

After a talk, it makes more sense to me to set emtpy string, instead of null, for the test.

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.

Seems fine for me 👍

@sonarqubecloud

sonarqubecloud Bot commented Sep 4, 2026

Copy link
Copy Markdown

@ivan-risueno
ivan-risueno merged commit eea203a into master Sep 4, 2026
3 checks passed
@ivan-risueno
ivan-risueno deleted the bugfix/component_url-not-getting-stored-anymore branch September 4, 2026 09:49
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.

2 participants