5 Application Identity

Racket

5 Application Identity🔗ℹ

package: rivet

struct
(struct app-info ( name
display-name
version
build
identifier
release-channel))
  name : string?
  display-name : string?
  version : string?
  build : exact-positive-integer?
  identifier : string?
  release-channel : symbol?

#:transparent] { Represents the release identity staged from "rivet.rktd".}

procedure
(current-app-info) → app-info?

Reads and validates the identity for the running application.

procedure
(app-name) → string?

Returns the configured project name.

procedure
(app-display-name) → string?

Returns the user-visible application name.

procedure
(app-version) → string?

Returns the application release version.

procedure
(app-build) → exact-positive-integer?

Returns the application build number.

procedure
(app-identifier) → string?

Returns the application/bundle identifier.

procedure
(app-release-channel) → symbol?

Returns 'stable, 'beta, or 'dev.

The build writes "rivet-app-info.rktd" into the application resource root on every platform. The procedures fail explicitly when that generated file is absent or malformed, so update checks cannot silently use a stale hardcoded fallback.

1	Installation
2	Architecture and Module Boundaries
3	Finding and Integrating Missing Capabilities
4	Application Backend
5	Application Identity
6	System Services
7	Distribution and Secure Updates
8	Command-Line Workflow
9	Further Reading