open-index/open-npm huggingface dataset:
npm package: @krzysztofkarol/material-ui-fullscreen-dialog
Description: A fullscreen dialog for Material-UI.
Author: Wertarbyte
Latest version: 0.6.2

# material-ui-fullscreen-dialog
This project provides a [fullscreen dialog][dialogspec] for [Material-UI][mui].

![Demo](demo.gif)

If you want to try the component yourself instead of watching a gif, head over to [the storybook][gh-pages] for a live demo!

## Installation
```shell
npm i --save material-ui-fullscreen-dialog
```

## Usage


```jsx
import FullscreenDialog from 'material-ui-fullscreen-dialog'

<FullscreenDialog
  open={this.state.open}
  onRequestClose={() => this.setState({ open: false })}
  title={'Demo dialog'}
  actionButton={<FlatButton
    label='Done'
    onClick={() => this.setState({ open: false })}
  />}
>
  // dialog content here
</FullscreenDialog>
```

## Properties
| Name | Type | Default | Description |
| --- | --- | --- | --- |
| actionButton | `node` | | A `FlatButton` or `IconButton` that is used as affirmative action button. |
| appBarStyle | `object` | | Overrides the inline-styles of the app bar. | 
| appBarZDepth | `number` | 1 | Overrides the z-depth of the app bar, will affect its shadow. This is ignored if immersive is set to `true`. |
| children | `node` | | Children elements. |
| closeIcon | `node` | Close icon | Icon element used for the dismissive action. This is hidden if `onRequestClose` is not set. |
| containerStyle | `object` | | Overrides the inline-styles of the dialog's children container. |
| immersive | `bool` | `false` | Toggles the immersive mode. If set to `true`, the app bar has a semi-transparent gradient and overlays the content. |
| onRequestClose | `function` | | Callback that is invoked when the dismissive action button is touched. |
| open * | `bool` | | Controls whether the dialog is opened or not. |
| style | `object` | | Overrides the inline-styles of the dialog's root element. |
| title | `string` | | The title of the dialog. |
| titleStyle | `object` | | Overrides the inline-styles of the app bar's title element. |

\* required property

## Credits
The code for the animation was adapted from Material UI's [Dialog][mui-dialog], although the animation itself is different.

## License
The files included in this repository are licensed under the MIT license.

[dialogspec]: https://material.io/guidelines/components/dialogs.html#dialogs-specs
[mui]: http://www.material-ui.com/#/
[gh-pages]: https://teamwertarbyte.github.io/material-ui-fullscreen-dialog/
[mui-dialog]: https://github.com/callemall/material-ui/blob/master/src/Dialog/Dialog.js
npm package: @krzysztofkarol/swagger-to-graphql
Description: Swagger2GraphQL converts your existing Swagger schema to GraphQL types where resolvers perform HTTP calls to certain real endpoints. It allows you to move your API to GraphQL with nearly zero afford and maintain both: REST and GraphQL APIs.
Author: Roman Krivtsov
Latest version: 1.1.7

# Swagger2GraphQL

Swagger2GraphQL converts your existing Swagger schema to GraphQL types where resolvers perform HTTP calls to certain real endpoints.
It allows you to move your API to GraphQL with nearly zero afford and maintain both: REST and GraphQL APIs.

<a href="https://medium.com/@raxwunter/moving-existing-api-from-rest-to-graphql-205bab22c184">Why?</a>

# Usage

## Basic server

```js
const express = require('express');
const app = express();
const graphqlHTTP = require('express-graphql');
const graphQLSchema = require('swagger-to-graphql');

graphQLSchema('./petstore.json').then(schema => {
  app.use('/graphql', graphqlHTTP(() => {
    return {
      schema,
      context: {
        GQLProxyBaseUrl: API_BASE_URL
      },
      graphiql: true
    };
  }));

  app.listen(3009, 'localhost', () => {
    console.info(`API is here localhost:3009/graphql`);
  });
}).catch(e => {
  throw e;
});
```

## CLI convertion

```
npm i -g swagger-to-graphql
swagger-to-graphql --swagger=/path/to/swagger_schema.json > ./types.graphql
```
## Authorization

```
 ...
  context: {
    GQLProxyBaseUrl: API_BASE_URL,
    BearerToken: req.get('authorization')
  },
 ...
```

<a href="https://github.com/yarax/swagger-to-graphql/blob/master/src/types.js#L3"> All context options </a>
npm package: @krzysztofkosek/generateid
Description: Simple Id generator
Latest version: 1.0.2

Simple Id generator

Usage:

const shortid = require('@krzysztofkosek/generateid');
 
console.log(shortid.generate(length));
 
 // length - the length of the generated string (integer)

 Example:

 const shortid = require('@krzysztofkosek/generateid');
 
console.log(shortid.generate(5));

//return AcXiG
npm package: @ks-ai/kclaw-container-bridge
Description: Bridges the gap between host paths and container paths for OpenClaw (KClaw) instances running in Docker.
Latest version: 1.0.0

# @ks-ai/kclaw-container-bridge

An [OpenClaw](https://github.com/openclaw) plugin that bridges the gap between host machine paths and Docker container paths for KClaw instances.

When running an AI coding assistant inside a Docker container, the AI perceives container-internal paths (e.g. `/workspace`) while users naturally refer to their host machine paths (e.g. `/home/user/my-project`). This mismatch causes the AI to misinterpret file locations.

This plugin injects a **path mapping table** into the system prompt before each request, enabling the AI to correctly translate and operate on file paths.

## Installation

### Option 1: OpenClaw CLI (recommended)

```bash
npx openclaw plugins install @ks-ai/kclaw-container-bridge
```

Or if you have the `openclaw` CLI installed globally:

```bash
openclaw plugins install @ks-ai/kclaw-container-bridge
```

### Option 2: Manual

Copy the plugin folder into your OpenClaw project's `extensions/` directory:

```
/path/to/openclaw/extensions/kclaw-container-bridge/
```

Ensure the folder contains `package.json` and `openclaw.plugin.json`.

## Configuration

Add the plugin entry to your `openclaw.json`:

```json
{
  "plugins": {
    "entries": {
      "kclaw-container-bridge": {
        "enabled": true,
        "config": {
          "mappings": [
            {
              "host": "/home/user/code/my-app",
              "container": "/workspace"
            },
            {
              "host": "/home/user/data",
              "container": "/mnt/data"
            }
          ]
        }
      }
    }
  }
}
```

Multiple mount points are supported. The plugin always resolves using the most specific (longest) matching prefix.

## Environment Variable Fallback

If no mappings are configured in `openclaw.json`, the plugin falls back to environment variables:

| Variable | Description |
|:---|:---|
| `KCLAW_PATH_MAPPINGS` | JSON array of `{ host, container }` objects |
| `KCLAW_HOST_WORKSPACE` | Single host workspace path |
| `KCLAW_CONTAINER_WORKSPACE` | Corresponding container path (default: `/workspace`) |

**Example:**

```bash
export KCLAW_PATH_MAPPINGS='[{"host":"/home/user/project","container":"/workspace"}]'
```

## How It Works

1. **Load configuration** — reads `mappings` from `openclaw.json` plugin config, falls back to environment variables.
2. **Build context** — generates a Markdown path mapping table along with operational guidelines for the AI.
3. **Inject into prompt** — uses the `before_prompt_build` hook to append the context block to the system prompt before every request.

## License

MIT