casey / casey/x-serialization-format

Cope with crate renames

Open
#16 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
1
Forks
1
PR merge metrics
No merged PRs in 30d

Description

`data` is a common word, so we should expect that sometimes the crate will be renamed. We should deal with this in macros and indirect through `Cargo.toml`.

Contributor guide

No contributing guide indexed for this repository

Research direction

Inspect the macros and Cargo.toml handling first to understand how the crate name is referenced and how a renamed crate should be supported. Done means the macros work when the crate is renamed and dependency handling goes through Cargo.toml as requested; the issue names no tests or specific entry points.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.