Skip to content
This repository has been archived by the owner on Jun 26, 2018. It is now read-only.

sassmanifest.json #6

Open
jlong opened this issue Oct 18, 2013 · 6 comments
Open

sassmanifest.json #6

jlong opened this issue Oct 18, 2013 · 6 comments
Milestone

Comments

@jlong
Copy link
Contributor

jlong commented Oct 18, 2013

Merge in work from:

https://github.com/jhardy/sassy-toolbox-rails

Example sassmanifest.json:

{
  "name": "Ceaser Easing",
  "version": "1.0.1",
  "description" : "Awesome transitions for you to use",
  "tags": ["transitions", "easing", "animations"],
  "supports": ">= 3.0.1", // requires Sass 3.0.1 or above
  "homepage_url": "http://ceasersass.com",
  "documentation_url": "http://ceasersass.com/docs"
}
@jlong
Copy link
Contributor Author

jlong commented Oct 26, 2013

Here's the schema for the current extensions table here:

create_table "extensions", force: true do |t|
    t.string   "name"
    t.string   "description",               limit: 1000
    t.text     "installation_instructions"
    t.string   "supports_sass_version"
    t.string   "repository_url"
    t.string   "repository_type"
    t.string   "download_url"
    t.string   "download_type"
    t.string   "homepage_url"
    t.string   "current_version"
    t.integer  "author_id"
    t.datetime "created_at"
    t.datetime "updated_at"
  end

@jlong
Copy link
Contributor Author

jlong commented Oct 26, 2013

Wondering if this should maybe be called "sassext.json" ?

@carwin
Copy link
Contributor

carwin commented Oct 29, 2013

I think sassmanifest.json feels more comfortable.

@jhardy
Copy link

jhardy commented Oct 29, 2013

I feel sasstext.json doesn't really describe its purpose, I think sassmanifest.json or even sassregistry.json feels better.

@jlong
Copy link
Contributor Author

jlong commented Oct 29, 2013

The reason I bring this up is I think we also need a sass.json for the command-line tool that holds Sass extension configuration, much like compass.rb does for Compass. This may be crazy talk though. :)

@carwin
Copy link
Contributor

carwin commented Oct 29, 2013

Unless I'm missing something, the name of that config file could easily be renamed if it ends up in conflict with another file. I don't think I'd worry too much about it now.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants