open-index/open-npm huggingface dataset:
npm package: @sg0/sg-naming
Description: The naming convention for SG.
Author: Brian C Sparks
Latest version: 1.0.10

# sg-naming

The naming convention for SG.

## Simple

```
[upstream...] / Package: [sub-packages...] / project: [sub-projects...] / version / variation / [item-names...] (= item-value)

 - or -

[upstream...] / Project: [sub-projects...] / package: [sub-packages...] / version / variation / [item-names...] (= item-value)
```

* Upstream is not our concern, but it exists.
* Since the package is the one using the namespacing, the `package` and `sub-packages` are known.
* A place for sub-packages
  * But in reality, this will usually get folded into the parent.
* The specific project
* A place for sub-projects
  * But in reality, this will usually get folded into the parent.
* The item's version number
  * Semantic numbering, but each digit has a default ([0.0.1]), but can be written many ways, like v1_2
* The item's variation (aka 'stage' or 'build')
  * Most if not all items share the path, but they don't have to (default to `demo`)
* After our segment, there are possibly infinite more path segments, but we are not in control of
  them.

## Well Known Formats

* Redis uses colons.
* Windows uses back-slashes
* The rest of the world uses forward slashes.
* Etc.
npm package: @sg60/sanity-rich-date-input
Description: A timezone-aware datetime type and input component for Sanity Studio
Author: Sanity.io
Latest version: 3.0.6

> For the v2 version, please refer to the [studio-v2 branch](https://github.com/sanity-io/rich-date-input/tree/studio-v2).

# V3 Rich Date Input

Provides a timezone-aware date input for Sanity Studio.

![This is an image](assets/plugin.gif)

## Installation

```sh
npm install @sanity/rich-date-input
```

## Usage

Add it as a plugin in `sanity.config.ts` (or .js):

```ts
import {defineConfig} from 'sanity'
import {richDate} from '@sanity/rich-date-input'

export default defineConfig({
  // ...
  plugins: [richDate()],
})
```

Then, use `richDate` as a type in your schema:

```ts
import {defineField, defineType} from 'sanity'

export default defineType({
  name: 'event',
  title: 'Event',
  type: 'document',
  fields: [
    defineField({
      name: 'scheduledAt',
      title: 'Scheduled at',
      type: 'richDate',
      // this will take the same options available on the datetime type: https://www.sanity.io/docs/datetime-type
      options: {
        timeStep: 30,
      },
    }),
  ],
})
```

When a user selects a date, the timezone will be stored in the document. They can choose a different timezone, if desired. The date displayed will be the time as it would be in that timezone. UTC will be calculated from the timezone and local time.

The typical data output should be:

```ts
{
  _type: 'richDate',
  local: '2023-02-21T10:15:00+01:00',
  utc: '2023-02-12T09:15:00Z',
  timezone: 'Europe/Oslo',
  offset: 60
}
```

## License

[MIT](LICENSE) © Sanity.io

## Develop & test

This plugin uses [@sanity/plugin-kit](https://github.com/sanity-io/plugin-kit)
with default configuration for build & watch scripts.

See [Testing a plugin in Sanity Studio](https://github.com/sanity-io/plugin-kit#testing-a-plugin-in-sanity-studio)
on how to run this plugin with hotreload in the studio.

### Release new version

Run ["CI & Release" workflow](https://github.com/sanity-io/v3-rich-date-input/actions/workflows/main.yml).
Make sure to select the main branch and check "Release new version".

Semantic release will only release on configured branches, so it is safe to run release on any branch.
npm package: @sgadekar81/sails-elastic
Description: Elasticsearch adapter for Sails / Waterline
Author: Mohamed Elawadi
Latest version: 0.13.0

# waterline-elasticsearch

[![Join the chat at https://gitter.im/mie00/sails-elasticsearch](https://badges.gitter.im/mie00/sails-elasticsearch.svg)](https://gitter.im/mie00/sails-elasticsearch?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)

### Installation

To install this adapter, run:

```sh
$ npm install sails-elastic
```


### Configuration

#### config/connections.js

```js
{
    adapter: 'sails-elastic',
    hosts: ['http://127.0.0.1:9200'],
    keepAlive: false,
    sniffOnStart: true,
    maxRetries: 10,
    deadTimeout: 40000,
    sniffOnConnectionFault: true,
    apiVersion: '2.0'
},
```
#### Models

##### Attributes

sails-elastic does not support `attributes` inside the model. It gets its attributes from another attribute in the model called `elasticSearch`. There you can tell elasticsearch how to create the index. You can find more information [here](https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-create-index.html).

```js
// person model
module.exports = {
    elasticSearch: {
        mappings: {
            person: {
                properties: {
                    name: {
                        type: "string",
                    },
                    adress: {
                        type: "string",
                        index: "not_analyzed"
                    },
                    age: {
                        type: "integer",
                    },
                }
            }
        }
    }
};
```

##### Multiple adapters

To use multiple adapters for the same model. you have to make elasticsearch the last one, and manually sync create, update, destroy between adapters

```js
module.exports = {
    connection: ['mongoConnection','elasticConnection'],
    elasticSearch: {/*...*/},
    attributes: {/*...*/},
    afterCreate: function (value, callback){
        this.createIndex(value, callback)
    },
    afterUpdate: function (value, callback){
        this.updateIndex(value.id, value, callback)
    },
    afterDestroy: function (value, callback){
        this.destroyIndex(value.id, callback)
    },
};
```

> Warning: for sails v11.0 and earlier, connection attribute used to be defined with an 's'.

### API

This adapter exposes the following methods (you can pass a callback function to them or use them as [bluebird](https://github.com/petkaantonov/bluebird) promises):

* `search(criteria, callback)`

* `createIndex(value, callback)` === `create(value, callback)`

* `updateIndex(id, value, callback)` === `update(id, value, callback)`

* `destroyIndex(id, callback)` === `destroy(id, callback)`

* `countIndex(criteria, callback)` === `count(criteria, callback)`

* `bulk(body, callback)`

* `client()`

+ **returns**
  + Elasticsearch client instance to call methods directly to elasticsearch API. You can find API reference [here](https://www.elastic.co/guide/en/elasticsearch/client/javascript-api/current/api-reference.html)

### TODO

Fully support Semantic and Queryable interfaces.