Skip to content

feat: Rely on the network launcher to report whether friendly domains are supported#412

Open
adamspofford-dfinity wants to merge 3 commits intomainfrom
spofford/precise-friendly-domains
Open

feat: Rely on the network launcher to report whether friendly domains are supported#412
adamspofford-dfinity wants to merge 3 commits intomainfrom
spofford/precise-friendly-domains

Conversation

@adamspofford-dfinity
Copy link
Contributor

No description provided.

@adamspofford-dfinity adamspofford-dfinity marked this pull request as ready for review March 5, 2026 15:46
@adamspofford-dfinity adamspofford-dfinity requested a review from a team as a code owner March 5, 2026 15:46
root_key: local_root_key.clone(),
api_url: Url::parse("http://localhost:8000").unwrap(),
http_gateway_url: None,
use_friendly_domains: false,
Copy link
Contributor

Choose a reason for hiding this comment

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

The test changes only add use_friendly_domains: false to existing constructors. There's no test that exercises the true path to verify friendly domain URLs are actually printed in print_canister_urls.

use_friendly_domains: launcher_status
.supported_features
.iter()
.any(|f| f == "custom-domains"),
Copy link
Contributor

Choose a reason for hiding this comment

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

The feature name "custom-domains" appears as a raw string in both docker.rs and launcher.rs. Consider extracting to a constant to avoid typo-related bugs.

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