clockworklabs / clockworklabs/SpacetimeDB

Discuss whether to keep ScheduleAt-to-ulong conversion methods

Open
#2,171 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
25.2k
Forks
1.1k
Avg merge
2d 7h
Merged PRs (30d)
46

Description

wrt mild changes to the tutorial

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the tutorial changes mentioned in the issue and locating the ScheduleAt-to-ulong conversion methods. Compare their current use in the tutorial and surrounding code, then document a clear decision on whether the methods should remain; the issue provides no file or test path.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.