open-index/open-npm huggingface dataset:
npm package: @phoenix-plugin-registry/brackets-workspaces
Description: Create and manage your workspaces directly in Brackets.
Author: thomasvalera
Latest version: 2.1.3

Brackets Workspaces
===================

Are you not tired of having to use the "New Brackets Window" button every time you start Brackets?
Have you never dreamed of being able to open Brackets and have all your windows opened in only 2 clicks??
With Brackets Workspaces you will forget this button ever existed and live your dream!

This extension defines a "workspace" as a set of windows to be opened.

Features
===================

* Easy access to all your workspaces  
![Menu Bar Access](https://raw.github.com/thomasvalera/Brackets-Workspaces/master/images/Workspaces-2.1.2.png)

* Manage all your workspaces  
![Workspaces Manager](https://raw.github.com/thomasvalera/Brackets-Workspaces/master/images/Workspaces-manage.png)

* Modified version of MainWindow  
    https://github.com/thomasvalera/Brackets-MainWindow

How To
===================

Install
------------------

1. Choose _File > Extension Manager_ and select the _Available_ tab.
2. Search for _Workspaces_.
3. Hit _Install_!

Alternatively:

1. Go to _File > Extension Manager_ and select _Install from URL..._.
2. Copy and paste the following: https://github.com/thomasvalera/Brackets-Workspaces.
3. Hit _Install_!

How to add a workspace
------------------
* Go to _Workspaces > Manage Workspaces_.
* In the popup, select the _Add_ tab.
* There, fill in the name of your workspaces and a small description to help you remember.
* At the bottom, select the _Add Folder_ button to add the folder you wish to be opened in the workspace.
* Finally, hit _Submit_ to create your workspace.

NOTE:

* Workspaces containing no folders are not displayed in Brackets' menu under _Workspaces_.
* Each folder is opened in a separate window.

How to modify an existing workspace
------------------
* Go to _Workspaces > Manage Workspaces_.
* Search for the workspace you wish to modify and hit _Modify_.

How to remove an existing workspace
------------------
* Go to _Workspaces > Manage Workspaces_.
* Search for the workspace you wish to remove and hit _Remove_ ... twice ... just to be sure.

FAQ
===================
* It doesn't work ?@!@#!
  - It hasn't been fully tested yet, so you might have found a bug! If you think you have, open a new Issue an I will try to fix the problem as soon as possible!

* Does he know how awesome this extension is?
  - You tell me! If you like this extension I would be happy to hear your thoughts about it, send me an email at thomasvalera@gmail.com!

Contact
===================
If you want to contribute, ask some questions or even discuss possible features to add, open an _enhancement_ ticket or send me an email at thomasvalera@gmail.com.
npm package: @phoenix-plugin-registry/brackets-wp-functions-hint
Description: Brackets Wordpress Hint - plugin for Brackets, which will help you in writing Wordpress Themes/Plugins (WooCommerce, ACF included)
Author: Arsmoon
Latest version: 4.0.3

# Brackets WordPress Hint

# [![Downloads](https://badges.ml/brackets-wp-functions-hint/total.svg)](https://brackets-extension-badges.github.io#brackets-wp-functions-hint)

Brackets extension, which helps you in writing WordPress Themes/Plugins.

## Plugin include hints for:

- WordPress Core functions <br>
  _read more [Wordpress Reference](https://developer.wordpress.org/reference/)_
- Advanced Custom Fields functions <br>
  _read more [ACF Resources](http://www.advancedcustomfields.com/resources/)_
- WooCommerce functions <br>
  _read more [API Docs](https://docs.woothemes.com/wc-apidocs/)_

## How to Sync new functions?

In window Menu:

> - Help
> - Show Extensions Folder
> - Go to "Brakets-wp-hint"
> - Run `npm i` then `npm run sync` (if node_modules are installed);
> - Wait for sync completed.

## License

Copyright (c) 2019, [Arsmoon](https://arsmoon.com/?utm_source=github&utm_medium=article&utm_campaign=brackets-wp-hints&utm_content=readme "Arsmoon")

> See LICENSE for more info.

## Donate

[Support plugin](https://send.monobank.com.ua/QMnpw2tn "Support plugin")

---

If you have any questions on this please post an issue/question: https://github.com/Tusko/brackets-wp-hint/issues
npm package: @phoenix-plugin-registry/brackets-yaml-linter
Description: Provides linting functionality for YAML files
Author: Samuel Lai
Latest version: 1.0.0

brackets-yaml-linter
====================

This is an extension for the [Brackets](http://brackets.io) editor that provides linting functionality for YAML files.

To install, simply look for this extension in the Brackets extension manager.

This extension uses a modified, bundled version of [js-yaml](https://github.com/nodeca/js-yaml) to parse the YAML file. The modification makes js-yaml emit a warning when a key is re-defined in a mapping, e.g.

```yaml
days_of_the_week:
  Monday: 1
  Tuesday: 2
  Wednesday: 3
  Thursday: 4
  Friday: 5
  Saturday: 6
  Sunday: 7
  Monday: 1
```

will cause a warning to be emitted because `Monday` has been defined twice. This was added because it is a common mistake that can be frustrating to trouble-shoot.
npm package: @phoenix-plugin-registry/brackets-yuidoc-ext
Description: Inserts YUIDoc comment blocks when you select/highlight a function or property. Use Ctr+Alt+Y and a YUIDoc comment block will be inserted with the correct function/property names. Provides the starting framework within which you can then edit things such 
Author: mikey.zhaopeng
Latest version: 1.1.0

# Brackets-yuidoc


[Brackets](http://brackets.io/) extension for inserting [YUIDoc](http://yui.github.io/yuidoc/syntax/) comment blocks. Works with JS, CoffeeScript and ES6.

## Usage


In the Brackets editor, select/highlight the property or method that you want to document then either select from the edit menu "Insert YUIDoc property" or use the shortcut keys Ctrl+Alt+Y. A YUIdoc comment block *boilerplate* will be inserted with property/method names etc filled in.

```
/**
* Description for init
* @private
* @method init
* @param {Object} params
* @return {Object} description
*/
function init(params) {

}



/**
* Description for init 
* @private
* @method init 
* @param {Object} params
* @return {Object} description
*/
init = function (params) {

}



/**
* Description for init 
* @private
* @method init 
* @param {Object} params
* @return {Object} description
*/
this.init = function (params) {

}



/**
* Description for init
* @private
* @method init
* @param {Object} params
* @return {Object} description
*/
this.init: function (params) {

}

```

As you can see from the example, all properties and methods will be labeled as *private*. The extension has no real way of telling if a property is private or not, so by default it labels everything as *private*. The assumption is that it is easier to remove the tag than it is to type it in. For similar reasons, all parameter types are *Objects* and you will need to edit this if that is wrong. Likewise, the description will also need to be edited and a decision made whether you need the return tag and, if so, whether you want a description for the return.


![demo1](https://raw.githubusercontent.com/zhaopengme/brackets-yuidoc-ext/master/demo1.gif)

![demo2](https://raw.githubusercontent.com/zhaopengme/brackets-yuidoc-ext/master/demo2.gif)

![demo3](https://raw.githubusercontent.com/zhaopengme/brackets-yuidoc-ext/master/demo3.gif)

![demo4](https://raw.githubusercontent.com/zhaopengme/brackets-yuidoc-ext/master/demo4.gif)