ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

YAMLMacros

by Thom1729 ST2/ST3

A macro system for YAML files powered by Python. Intended for Sublime Text development.

Details

Installs

  • Total 173
  • Win 72
  • OS X 56
  • Linux 45
Aug 20 Aug 19 Aug 18 Aug 17 Aug 16 Aug 15 Aug 14 Aug 13 Aug 12 Aug 11 Aug 10 Aug 9 Aug 8 Aug 7 Aug 6 Aug 5 Aug 4 Aug 3 Aug 2 Aug 1 Jul 31 Jul 30 Jul 29 Jul 28 Jul 27 Jul 26 Jul 25 Jul 24 Jul 23 Jul 22 Jul 21 Jul 20 Jul 19 Jul 18 Jul 17 Jul 16 Jul 15 Jul 14 Jul 13 Jul 12 Jul 11 Jul 10 Jul 9 Jul 8 Jul 7 Jul 6
Windows 0 0 3 0 2 1 5 0 1 0 0 1 0 2 0 1 0 2 4 1 1 1 0 0 0 0 1 3 0 0 1 6 0 3 2 1 0 0 2 1 3 0 1 0 1 1
OS X 0 0 0 1 0 0 2 0 0 1 0 1 4 0 0 0 1 3 2 3 1 0 1 0 0 0 0 1 1 1 1 2 0 0 0 0 1 2 1 1 1 0 0 0 1 2
Linux 0 0 1 1 1 1 1 0 0 1 1 1 0 1 0 0 2 0 0 1 2 1 0 1 1 1 2 1 0 0 1 0 1 0 0 0 0 1 5 2 1 0 0 0 0 0

Readme

Source
raw.​githubusercontent.​com

YAML Macros

A macro system for YAML files powered by Python. Designed for Sublime Text syntax development.

Installation

YAML Macros can be installed via Package Control. You can also git clone this repository into your packages directory. If you do, rename it to “YAMLMacros”.

Overview

Sublime Text syntax definitions can often have a lot of boilerplate and repeated code. Consider this simple syntax that highlights SQL keywords:

%YAML 1.2
---
name: SQL Simple (YAML Macros example)
scope: source.sql
contexts:
  main:
  - match: \b(?i:select|from|where)\b
    scope: keyword.control.sql

  - match: \b(?i:distinct|as)\b
    scope: keyword.operator.word.sql

  - match: \b(?i:dual)\b
    scope: constant.language.sql

The same construct \b(?i:…)\b is repeated over and over. This can be tedious to write and annoying to read, and in a full, complex SQL syntax with a dozen or more similar matches, it's not unlikely that a hard-to-spot typo will lead to a hard-to-detect bug, such as a keyword only working in lowercase. With YAML Macros, you can DRY up your syntax by factoring out common idioms:

%YAML 1.2
%TAG ! tag:yaml-macros:sql_simple_macros:
---
name: SQL Simple (YAML Macros example)
scope: source.sql
contexts:
  main:
    - match: !word select|from|where
      scope: keyword.control.sql

    - match: !word distinct|as
      scope: keyword.operator.word.sql

    - match: !word dual
      scope: constant.language.sql

Then, in sql_simple_macros.py:

def word(str):
    return r'\b(?i:%s)\b' % str

It's as simple as that! For a more complex use case that uses a number of macros, see the full SQL example.

Usage

Importing macros

To import macros into your YAML file, add a %TAG directive at the top referencing the file containing your macros. The syntax is as follows:

%TAG <tag handle> tag:yaml-macros:<macro package>:

<tag handle> is the prefix you will use to invoke your macros. It must begin with an exclamation point. <macro package> is path to your macro definitions file. You can use multiple macro definitions files; simply write two %TAG directives with different tag handles.

Invoking macros

You may invoke a macro anywhere in your YAML file a value is expected:

<tag handle><macro name> <value>

Examples:

!word select
!expect [ ';', 'punctuation.terminator.statement.sql' ]

Note that there is no space between the tag handle and the name of a macro.

Defining macros

A macro definitions file is any Python module. It may be as simple as a single function definition or as complex as you like. If Python can do it, you can put it in a macro.

If a macro is applied to a YAML list, each list item will be passed as an argument. If a macro is applied to a YAML dictionary, each item will be passed as a keyword argument. Otherwise, the macro will receive a single value.

Applying your macros

If you have named your file with a .yaml-macros extension, simply select the “YAML Macros” build system. Running the build will create a compiled YAML file at the same location without the extra .yaml-macros suffix.

Command line interface

There is a basic command line interface. The CLI expects your YAML Macros file as standard input and will send the compiled YAML file to standard output. Paths will be resolved relative to your working directory.