tmspzz/Rome

Add a command to verify several properties of a framework

Open

#50 opened on Mar 23, 2017

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Haskell (771 stars) (54 forks)batch import
advancedenhancementgood first issuehelp wantedintermediate

Description

Enhancement Suggestion

Add a command to verify several properties of a framework

Steps which explain the enhancement

A verify command with several switches could be added to:

  • verify properties contained in the Info.plist of a framework
    • verify that a framework is actually at the version it claims to be in the cache
    • verify that a framework is built by a specific user
    • eventually give the users the possibility to verify any property (maybe come up with a DSL for this)
  • verify that the she256 hash of a framework matches the sha256 hash in the Carthage Version file for that framework

Current and suggested behavior

No verification is performed at the moment. Verification of some kind, along the lines of the suggestions above can be performed.

Why would the enhancement be useful to most users

Verifying properties of a framework present in the cache give the users move confidence in the cached frameworks.

Contributor guide

Tech stack
None
Domain
clitoolingrelease
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
familiarity with Carthagebasic Haskellunderstanding of framework metadata
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Examine the Rome codebase structure, particularly how existing commands are implemented (e.g., the 'cache' command). Review the Carthage Version file format and Info.plist to understand the properties to verify. Look at any existing tests or patterns for adding new commands. Consider whether a DSL is necessary or if simple flags suffice. Assess the effort for implementing sha256 verification against the Version file.