Skip to content

Simplified module/package structure #701

@bplommer

Description

@bplommer

When trialling t4c at $work I've had a lot of complaints about the number of different packages and modules that are needed for the core functionality. Here are a few tentative suggestions for reducing barriers to adoption:

modules

  • combine model into kernel
  • combine exporter-common, base and inject into core

packages

  • move contents of model and inject packages into either the base package or trace and span packages
  • move contents of kernel package into either the base package or a span package
  • consider changing the base package from io.janstenpickle.trace4cats to just trace4cats

Any thoughts on this?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions