Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Config Files #2

Open
callil opened this issue Feb 18, 2018 · 1 comment
Open

Config Files #2

callil opened this issue Feb 18, 2018 · 1 comment
Assignees
Labels
core Topics specific to the core codebase. enhancement New feature or request

Comments

@callil
Copy link

callil commented Feb 18, 2018

Each tool should have to define a content type it is available for. For instance, print-arena should only be invoked on channels.

for instance:

  "name": "Print Are.na",
  "version": "0.1.0",
  "description": "Generate a PDF from your channels",
  "contentTypes": ["channels"]

or something to this effect. Then this can get used here maybe?

config = require 'configuration.json'
newTool( 'arena_toolkit_music' ,  config);
@callil callil changed the title Content type awareness Config Files -- Content type awareness Feb 18, 2018
@callil callil changed the title Config Files -- Content type awareness Config Files Feb 18, 2018
@hxrts hxrts self-assigned this Feb 20, 2018
@hxrts hxrts added core Topics specific to the core codebase. enhancement New feature or request labels Feb 26, 2018
@g-a-v-i-n
Copy link

I propose we use something like the validator config for this config file:

const config = {
    whitelists: {
      class: ['Attachement', 'Media'],
      providerName: ['YouTube', 'Vimeo', 'SoundCloud'],
      extension: ['mp3', 'flac', 'wav'],
      state: ['available'],
    },
    match: {
      hasLargeImage: block => testImageSize(block),
    },
}

this way the config is extensible with custom match tests

@hxrts hxrts mentioned this issue Feb 28, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core Topics specific to the core codebase. enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants