npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@grupojaque/model-files

v1.0.2

Published

Provides functions to manage files licked to models.

Downloads

9

Readme

Model Files

Provides functions to validate and store files in server, while managing the related models and generating paths.

This service was developed according to the following documentaition.

Setup

Requirements

Modules

Initialization

Install with:

$ npm install @grupojaque/gcs-file

Import in project:

ModelFiles = require('@grupojaque/model-files')(configObject);

configObject Object with configuration. Explained below

models The models created by Sequelize

When required will return the GCSFile to be used as explained below.

Configuration

Configuration object

An object with the following data must be provided when the module is imported.

| Key | Description | | ---- | ----------- | | modelFiles | Object with the definitions of the models using files. | | types | Definition of all the possible types used in the modelFiles descriptions. | | tasks | The configured tasks to be used before storing | | filesDir | Directory to store files, defaults to assets | | getPath | Function to return the path given the gcsFile as parameter | | getModelName | Function to return the model name of a given instance |

modelFiles

Each key of the object must be the name of the model, the value is an object containing as keys the names of the attributes which store the file info. This keys do not contain the prefix. Each attribute configuration must have the following.

| Key | Description | | ---- | ----------- | | type | String that identifies the type configuration of the file.| | options | Object with the options of the attribute, used for tasks and procedures. | | beforeStore | Array of procedures names that must be called before storing, this will be done after the procedures defined in the type |

types

Each type most have the following attributes. To complete this fields you can use this types-list.

| Key | Description | | ---- | ----------- | | mimeType | String to indicate the content MIME type of the file| | ext | String to indicate the file extension, including the . | | beforeStore | Array of procedures names that must be called before storing |

tasks

Each of the configured tasks will receive the gcsFile as parameter to use as convinent. This tasks must be synchronous and can throw a ModelFileError if required. The configured tasks can overwrite the default tasks.

You can also find a configuration example file here

Other configurations

A module to read files from the request might be necesary. The functions are expecting busboy-body-parser to manage this in a middleware.

If using Sails Js the config\http.js file must be edited to provide this.

Usage

Constructor

new GCSFile(modelInstance, fileName, inputFile, options)

Creates a new GCSFile object.

  • modelInstance: Model associated to the file. Must have an attribute called has_ + fileName. This attribute must be a boolean or a boolean array in case of a gallery.
  • fileName: Name of the file without extension. If the name has - it will be considered with the first part being the attribute name, and the second the index (starting in 1) to index the attribute gallery.
  • inputFile: Input file generated with busboy-body-parser. This is required if calling the store function.
  • options: Optional object that can be used in configuration functions, such as getPath or any task.

Instance functions

store()

Runs all the tasks indicated in the beforeStore array, if all are successful, stores the inputFile in the server. After doing so, updates the corresponding attribute in the model instance.

Errors

This function can throw all errors defined in the tasks.

remove()

Deletes the file from server. After doing so, updates the corresponding attribute in the model instance.

getFullUrl()

Gets the full url of the file. If no file stored, returns an empty string.

bucketName() + getPath()

Default tasks

The following tasks are given by default, they can be overwritten in the configuration file.

validateHasStoredData

Validates that there has been data stored.

Throws

| status | message | errorDetail | | ---------------------- | --------------------------| --------------------- | | unsupportedMediaType | Media type not supported | [unsupportedMediaType] |

validateExtension

Validates that the file MIME type is one of the accepted mimes.

Requires
  • acceptedMimes: Array in type options indicating the list of accepted MIMES.
Throws

| status | message | errorDetail | | ---------------------- | --------------------------| --------------------- | | unsupportedMediaType | Extension not supported | [unsupportedExtension, fileName, acceptedMimes] |

encode

If the image stored has a different extension than expected, encodes the image to the encondigFormat specified.

Requires
  • encodingFormat: Format for encoding indicated in the type.
  • encodingCompresionRate: Number indicating the compression rate indicated in the type.
validateExactDimentions

Validates that the image on the image are the same as those in options.

Requires
  • width: Key in options configuration for the attribute.
  • height: Key in options configuration for the attribute.
Throws

| status | message | errorDetail | | ---------------------- | --------------------------| --------------------- | | unsupportedMediaType | Dimensions must be exact | [unsupportedSize, fileName, expectedH, expectedW] |

validateNotBiggerSize

Validates that the image was not trucated.

Requires
  • width: Key in options configuration for the attribute.
  • height: Key in options configuration for the attribute.
Throws

| status | message | errorDetail | | ---------------------- | --------------------------| --------------------- | | unsupportedMediaType | Size is too big | [unsupportedSizeBig, fileName]` |

validateNotSmallerDimentions

Validates that the image has dimensions bigger than expected .

Requires
  • width: Key in options configuration for the attribute.
  • height: Key in options configuration for the attribute.
Throws

| status | message | errorDetail | | ---------------------- | --------------------------| --------------------- | | unsupportedMediaType | Dimentions are too small | [unsupportedSizeSmall, fileName, expectedH, expectedW] |

validateSameProportion

Validates that the image has the same proportion.

Requires
  • width: Key in options configuration for the attribute.
  • height: Key in options configuration for the attribute.
Throws

| status | message | errorDetail | | ---------------------- | --------------------------| --------------------- | | unsupportedMediaType | Invalid proportion | [unsupportedProportion, fileName, expectedH, expectedW] |

Errors

All errors in this module will be instances of ModelFileError, which extends the Error class with the following attributes.

  • name ModelFileError.
  • message: Message for user in english.
  • status: The HTTP status for the error.
  • errorDetail: Object with metadata specific for the error translation.

This errors can be manage by the ErrorHandler module by adding the following constructor in the module configuration.

ModelFileError: function(err, req) {
  return new ErrorHandler(err.status, err.message, null, err.errorDetail);
}

Contributors