pub struct TsGenerator { /* private fields */ }Implementations§
Source§impl TsGenerator
impl TsGenerator
Trait Implementations§
Source§impl CodeGenerator for TsGenerator
impl CodeGenerator for TsGenerator
Source§fn generate_project(
&self,
modules: &[(&AIRModule, &Path)],
) -> Result<GeneratedCode, CodegenError>
fn generate_project( &self, modules: &[(&AIRModule, &Path)], ) -> Result<GeneratedCode, CodegenError>
Emit a per-module native ES-module import tree (spec §20.6.1; DQ19
resolved): each reachable module → its own .ts file, cross-module
references resolved with real ESM import/import type. Mirrors the JS
backend’s per-module path (see crate::js) plus TS’s type level:
Optional/Result runtime types and concurrency/range runtime helpers
are emitted once into a shared _bock_runtime.ts, imported per file. The
minimal package.json {"type":"module"} run affordance — which makes
the .ts source tree run under node --experimental-strip-types — is
emitted by the scaffolder in project mode (S6a / DV18), not by codegen,
so --source-only output is bare source.
Output-path mapping is keyed on each module’s declared path
(module core.option ⇒ core/option.ts, imported "./core/option.ts" —
ESM specifiers reference the emitted .ts source directly so node
strip-types resolves them verbatim; tsc accepts the .ts extension via
rewriteRelativeImportExtensions, which also rewrites it to .js on
emit). The entry module is always main.ts.
Source§fn generate_tests(
&self,
modules: &[(&AIRModule, &Path)],
framework: &str,
) -> Result<TestArtifacts, CodegenError>
fn generate_tests( &self, modules: &[(&AIRModule, &Path)], framework: &str, ) -> Result<TestArtifacts, CodegenError>
Transpile @test functions into a Vitest/Jest bock.test.ts file (S7).
Identical in shape to the JS backend’s generate_tests (shared via
crate::generator::js_ts_generate_tests); only the file extension and
the concrete TS emit context differ. framework selects Vitest (default)
vs Jest.
Source§fn target(&self) -> &TargetProfile
fn target(&self) -> &TargetProfile
Source§fn generate_module(
&self,
module: &AIRModule,
) -> Result<GeneratedCode, CodegenError>
fn generate_module( &self, module: &AIRModule, ) -> Result<GeneratedCode, CodegenError>
Source§fn entry_invocation(&self, main_is_async: bool) -> Option<String>
fn entry_invocation(&self, main_is_async: bool) -> Option<String>
main function
as the entry point for this target, or None if the target has a
native entry-point convention (Rust fn main, Go func main) that
runs without a synthetic call. Read moreSource§impl Debug for TsGenerator
impl Debug for TsGenerator
Auto Trait Implementations§
impl Freeze for TsGenerator
impl RefUnwindSafe for TsGenerator
impl Send for TsGenerator
impl Sync for TsGenerator
impl Unpin for TsGenerator
impl UnsafeUnpin for TsGenerator
impl UnwindSafe for TsGenerator
Blanket Implementations§
Source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere
T: ?Sized,
Source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
Source§impl<T> Instrument for T
impl<T> Instrument for T
Source§fn instrument(self, span: Span) -> Instrumented<Self>
fn instrument(self, span: Span) -> Instrumented<Self>
Source§fn in_current_span(self) -> Instrumented<Self>
fn in_current_span(self) -> Instrumented<Self>
Source§impl<T> Paint for Twhere
T: ?Sized,
impl<T> Paint for Twhere
T: ?Sized,
Source§fn fg(&self, value: Color) -> Painted<&T>
fn fg(&self, value: Color) -> Painted<&T>
Returns a styled value derived from self with the foreground set to
value.
This method should be used rarely. Instead, prefer to use color-specific
builder methods like red() and
green(), which have the same functionality but are
pithier.
§Example
Set foreground color to white using fg():
use yansi::{Paint, Color};
painted.fg(Color::White);Set foreground color to white using white().
use yansi::Paint;
painted.white();Source§fn bright_black(&self) -> Painted<&T>
fn bright_black(&self) -> Painted<&T>
Source§fn bright_red(&self) -> Painted<&T>
fn bright_red(&self) -> Painted<&T>
Source§fn bright_green(&self) -> Painted<&T>
fn bright_green(&self) -> Painted<&T>
Source§fn bright_yellow(&self) -> Painted<&T>
fn bright_yellow(&self) -> Painted<&T>
Source§fn bright_blue(&self) -> Painted<&T>
fn bright_blue(&self) -> Painted<&T>
Source§fn bright_magenta(&self) -> Painted<&T>
fn bright_magenta(&self) -> Painted<&T>
Source§fn bright_cyan(&self) -> Painted<&T>
fn bright_cyan(&self) -> Painted<&T>
Source§fn bright_white(&self) -> Painted<&T>
fn bright_white(&self) -> Painted<&T>
Source§fn bg(&self, value: Color) -> Painted<&T>
fn bg(&self, value: Color) -> Painted<&T>
Returns a styled value derived from self with the background set to
value.
This method should be used rarely. Instead, prefer to use color-specific
builder methods like on_red() and
on_green(), which have the same functionality but
are pithier.
§Example
Set background color to red using fg():
use yansi::{Paint, Color};
painted.bg(Color::Red);Set background color to red using on_red().
use yansi::Paint;
painted.on_red();Source§fn on_primary(&self) -> Painted<&T>
fn on_primary(&self) -> Painted<&T>
Source§fn on_magenta(&self) -> Painted<&T>
fn on_magenta(&self) -> Painted<&T>
Source§fn on_bright_black(&self) -> Painted<&T>
fn on_bright_black(&self) -> Painted<&T>
Source§fn on_bright_red(&self) -> Painted<&T>
fn on_bright_red(&self) -> Painted<&T>
Source§fn on_bright_green(&self) -> Painted<&T>
fn on_bright_green(&self) -> Painted<&T>
Source§fn on_bright_yellow(&self) -> Painted<&T>
fn on_bright_yellow(&self) -> Painted<&T>
Source§fn on_bright_blue(&self) -> Painted<&T>
fn on_bright_blue(&self) -> Painted<&T>
Source§fn on_bright_magenta(&self) -> Painted<&T>
fn on_bright_magenta(&self) -> Painted<&T>
Source§fn on_bright_cyan(&self) -> Painted<&T>
fn on_bright_cyan(&self) -> Painted<&T>
Source§fn on_bright_white(&self) -> Painted<&T>
fn on_bright_white(&self) -> Painted<&T>
Source§fn attr(&self, value: Attribute) -> Painted<&T>
fn attr(&self, value: Attribute) -> Painted<&T>
Enables the styling Attribute value.
This method should be used rarely. Instead, prefer to use
attribute-specific builder methods like bold() and
underline(), which have the same functionality
but are pithier.
§Example
Make text bold using attr():
use yansi::{Paint, Attribute};
painted.attr(Attribute::Bold);Make text bold using using bold().
use yansi::Paint;
painted.bold();Source§fn rapid_blink(&self) -> Painted<&T>
fn rapid_blink(&self) -> Painted<&T>
Source§fn quirk(&self, value: Quirk) -> Painted<&T>
fn quirk(&self, value: Quirk) -> Painted<&T>
Enables the yansi Quirk value.
This method should be used rarely. Instead, prefer to use quirk-specific
builder methods like mask() and
wrap(), which have the same functionality but are
pithier.
§Example
Enable wrapping using .quirk():
use yansi::{Paint, Quirk};
painted.quirk(Quirk::Wrap);Enable wrapping using wrap().
use yansi::Paint;
painted.wrap();Source§fn clear(&self) -> Painted<&T>
👎Deprecated since 1.0.1: renamed to resetting() due to conflicts with Vec::clear().
The clear() method will be removed in a future release.
fn clear(&self) -> Painted<&T>
renamed to resetting() due to conflicts with Vec::clear().
The clear() method will be removed in a future release.
Source§fn whenever(&self, value: Condition) -> Painted<&T>
fn whenever(&self, value: Condition) -> Painted<&T>
Conditionally enable styling based on whether the Condition value
applies. Replaces any previous condition.
See the crate level docs for more details.
§Example
Enable styling painted only when both stdout and stderr are TTYs:
use yansi::{Paint, Condition};
painted.red().on_yellow().whenever(Condition::STDOUTERR_ARE_TTY);