Warp to Galaxy internal rebrand
This commit is contained in:
@@ -1,19 +0,0 @@
|
||||
//! Dev-channel `warp-tui` binary (internal nightly builds).
|
||||
//!
|
||||
//! Mirrors `app/src/bin/dev.rs`: loads the internal `dev` channel config and
|
||||
//! layers the dev feature flags, then hands off to the shared TUI entry point.
|
||||
|
||||
use anyhow::Result;
|
||||
use warp_core::channel::{Channel, ChannelState};
|
||||
use warp_core::features;
|
||||
|
||||
fn main() -> Result<()> {
|
||||
ChannelState::set(
|
||||
ChannelState::new(Channel::Dev, warp_channel_config::load_config!("dev"))
|
||||
.with_additional_features(features::DEBUG_FLAGS)
|
||||
.with_additional_features(features::DOGFOOD_FLAGS)
|
||||
.with_additional_features(features::PREVIEW_FLAGS),
|
||||
);
|
||||
|
||||
warp_tui::run()
|
||||
}
|
||||
@@ -1,23 +0,0 @@
|
||||
//! Local-channel `warp-tui` binary (internal dev builds).
|
||||
//!
|
||||
//! Mirrors `app/src/bin/local.rs`: loads the internal `local` channel config
|
||||
//! (via the `warp-channel-config` generator) and layers the dev feature flags,
|
||||
//! then hands off to the shared TUI entry point. Run it through
|
||||
//! `./script/run-tui`, which installs the generator first; running it directly
|
||||
//! without `warp-channel-config` on PATH will panic with install instructions.
|
||||
|
||||
use anyhow::Result;
|
||||
use warp_core::channel::{Channel, ChannelState};
|
||||
use warp_core::features;
|
||||
|
||||
fn main() -> Result<()> {
|
||||
ChannelState::set(
|
||||
ChannelState::new(Channel::Local, warp_channel_config::load_config!("local"))
|
||||
.with_additional_features(features::DEBUG_FLAGS)
|
||||
.with_additional_features(features::DOGFOOD_FLAGS)
|
||||
.with_additional_features(features::PREVIEW_FLAGS)
|
||||
.with_additional_features(features::LOCAL_FLAGS),
|
||||
);
|
||||
|
||||
warp_tui::run()
|
||||
}
|
||||
@@ -1,10 +1,9 @@
|
||||
//! OSS-channel `warp-tui` binary and `default-run` target.
|
||||
//!
|
||||
//! This is what bare `cargo run -p warp_tui` builds, so it hand-builds a
|
||||
//! production config and needs no internal `warp-channel-config` generator
|
||||
//! (mirrors `app/src/bin/oss.rs`). It is a console application (no GUI window,
|
||||
//! no app bundle), so unlike the GUI binaries it sets no `windows_subsystem`
|
||||
//! attribute and embeds no `Info.plist`.
|
||||
//! This is what bare `cargo run -p warp_tui` builds, so it hand-builds an
|
||||
//! OSS production config (mirroring `app/src/bin/oss.rs`). It is a console
|
||||
//! application (no GUI window, no app bundle), so unlike the GUI binaries it
|
||||
//! sets no `windows_subsystem` attribute and embeds no `Info.plist`.
|
||||
|
||||
use anyhow::Result;
|
||||
use warp_core::channel::{Channel, ChannelConfig, ChannelState, OzConfig, WarpServerConfig};
|
||||
@@ -14,7 +13,7 @@ fn main() -> Result<()> {
|
||||
let mut state = ChannelState::new(
|
||||
Channel::Oss,
|
||||
ChannelConfig {
|
||||
app_id: AppId::new("dev", "warp", "WarpTui"),
|
||||
app_id: AppId::new("com", "galaxy", "GalaxyOss"),
|
||||
logfile_name: "warp-tui.log".into(),
|
||||
server_config: WarpServerConfig::disabled(),
|
||||
oz_config: OzConfig::production(),
|
||||
|
||||
@@ -1,22 +0,0 @@
|
||||
//! Preview-channel `warp-tui` binary.
|
||||
//!
|
||||
//! Mirrors `app/src/bin/preview.rs`: loads the `preview` channel config and
|
||||
//! enables the preview feature flags (plus forced login), then hands off to the
|
||||
//! shared TUI entry point.
|
||||
|
||||
use anyhow::Result;
|
||||
use warp_core::channel::{Channel, ChannelState};
|
||||
use warp_core::features;
|
||||
|
||||
fn main() -> Result<()> {
|
||||
ChannelState::set(
|
||||
ChannelState::new(
|
||||
Channel::Preview,
|
||||
warp_channel_config::load_config!("preview"),
|
||||
)
|
||||
.with_additional_features(features::PREVIEW_FLAGS)
|
||||
.with_additional_features(&[features::FeatureFlag::ForceLogin]),
|
||||
);
|
||||
|
||||
warp_tui::run()
|
||||
}
|
||||
@@ -1,16 +0,0 @@
|
||||
//! Stable-channel `warp-tui` binary.
|
||||
//!
|
||||
//! Mirrors `app/src/bin/stable.rs`: loads the `stable` channel config with no
|
||||
//! additional feature flags, then hands off to the shared TUI entry point.
|
||||
|
||||
use anyhow::Result;
|
||||
use warp_core::channel::{Channel, ChannelState};
|
||||
|
||||
fn main() -> Result<()> {
|
||||
ChannelState::set(ChannelState::new(
|
||||
Channel::Stable,
|
||||
warp_channel_config::load_config!("stable"),
|
||||
));
|
||||
|
||||
warp_tui::run()
|
||||
}
|
||||
Reference in New Issue
Block a user