Jekyll 插件中的“优先级”标志应该如何工作？

我目前正在尝试为 Jekyll 开发一个插件，这将有助于使用云数对于响应式图像。当前源是在我的 Github 仓库中，稍后当/如果它有效时，我会将其变成宝石。

这个插件有两个特点：

• 用于定义 Cloudinary 图像的 Liquid 标签，例如{% cloudinary [preset] path/to/img.jpg [attr="value"] %}
• 一个转换器，可以选择自动将图像的标准 Markdown/Kramdown 语法转换为此 Liquid 标签：![alt text](path/to/img.jpg){:caption="caption text"}变成{% cloudinary path/to/img.jpg alt="alt text" caption="caption text" %}

目前，这两个功能都按预期工作，但它们没有“链接”。如果我在 Markdown 中使用 Liquid 标签，则会对其进行评估。如果我放置标准 Markdown 图像，它将转换为{% cloudinary … %}Liquid 标签，但该标签不被评估。

我怀疑这两个功能没有按正确的顺序运行，因此我想确保在评估 Liquid 标签之前执行 Converter。

但我还不明白如何使用优先级标志.

如果我取消注释the priority :normal我的插件中的行，然后运行bundle exec jekyll serve，我收到此错误：

$ bundle exec jekyll serve
Configuration file: /Users/nhoizey/Dropbox/Personnel/Devs/nicolas-hoizey.com/_config.yml
jekyll 3.1.6 | Error:  undefined method `priority' for Jekyll::CloudinaryTag:Class
Did you mean?  print

任何想法？

编辑（7 月 11 日）：

我现在已将其拆分为插件。

该转换器仍在我的网站中_plugins文件夹：https://github.com/nhoizey/nicolas-hoizey.com/blob/52c92a38410e133890eea6044a033cb20344b971/_plugins/cloudinaryfy.rb#L26

Jekyll 并没有抱怨这个“优先”标志。

Liquid 标签现在是一个真正的自治插件 gem，名为jekyll-cloudinary: https://nhoizey.github.io/jekyll-cloudinary/

如果我在这个插件中添加“优先”标志，我仍然会收到错误：

$ bundle exec jekyll serve                                                                                 bundler: failed to load command: jekyll (/usr/local/bin/jekyll)
Bundler::GemRequireError: There was an error while trying to load the gem 'jekyll-cloudinary'.
Gem Load Error is: undefined method `priority' for Jekyll::Cloudinary::CloudinaryTag:Class
Did you mean?  print
Backtrace for gem load error is:
/usr/local/lib/ruby/gems/2.3.0/gems/jekyll-cloudinary-1.2.2/lib/jekyll/cloudinary.rb:5:in `<class:CloudinaryTag>'
/usr/local/lib/ruby/gems/2.3.0/gems/jekyll-cloudinary-1.2.2/lib/jekyll/cloudinary.rb:4:in `<module:Cloudinary>'
/usr/local/lib/ruby/gems/2.3.0/gems/jekyll-cloudinary-1.2.2/lib/jekyll/cloudinary.rb:2:in `<module:Jekyll>'
/usr/local/lib/ruby/gems/2.3.0/gems/jekyll-cloudinary-1.2.2/lib/jekyll/cloudinary.rb:1:in `<top (required)>'
/usr/local/lib/ruby/gems/2.3.0/gems/jekyll-cloudinary-1.2.2/lib/jekyll-cloudinary.rb:1:in `require'
/usr/local/lib/ruby/gems/2.3.0/gems/jekyll-cloudinary-1.2.2/lib/jekyll-cloudinary.rb:1:in `<top (required)>'
/usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/runtime.rb:86:in `require'
/usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/runtime.rb:86:in `block (2 levels) in require'
/usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/runtime.rb:81:in `each'
/usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/runtime.rb:81:in `block in require'
/usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/runtime.rb:70:in `each'
/usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/runtime.rb:70:in `require'
/usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler.rb:102:in `require'
/usr/local/lib/ruby/gems/2.3.0/gems/jekyll-3.1.6/lib/jekyll/plugin_manager.rb:34:in `require_from_bundler'
/usr/local/lib/ruby/gems/2.3.0/gems/jekyll-3.1.6/bin/jekyll:9:in `<top (required)>'
/usr/local/bin/jekyll:22:in `load'
/usr/local/bin/jekyll:22:in `<top (required)>'
/usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/cli/exec.rb:63:in `load'
/usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/cli/exec.rb:63:in `kernel_load'
/usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/cli/exec.rb:24:in `run'
/usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/cli.rb:304:in `exec'
/usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
/usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
/usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/vendor/thor/lib/thor.rb:359:in `dispatch'
/usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/vendor/thor/lib/thor/base.rb:440:in `start'
/usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/cli.rb:11:in `start'
/usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/exe/bundle:27:in `block in <top (required)>'
/usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/friendly_errors.rb:98:in `with_friendly_errors'
/usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/exe/bundle:19:in `<top (required)>'
/usr/local/bin/bundle:22:in `load'
/usr/local/bin/bundle:22:in `<main>'
Bundler Error Backtrace:

  /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/runtime.rb:89:in `rescue in block (2 levels) in require'
  /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/runtime.rb:85:in `block (2 levels) in require'
  /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/runtime.rb:81:in `each'
  /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/runtime.rb:81:in `block in require'
  /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/runtime.rb:70:in `each'
  /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/runtime.rb:70:in `require'
  /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler.rb:102:in `require'
  /usr/local/lib/ruby/gems/2.3.0/gems/jekyll-3.1.6/lib/jekyll/plugin_manager.rb:34:in `require_from_bundler'
  /usr/local/lib/ruby/gems/2.3.0/gems/jekyll-3.1.6/bin/jekyll:9:in `<top (required)>'
  /usr/local/bin/jekyll:22:in `load'
  /usr/local/bin/jekyll:22:in `<top (required)>'

为什么它适用于一个插件而不适用于另一个？

我怎样才能确保cloudinarify转换器插件在之前运行jekyll-cloudinary液体标签是怎么解释的？

The priority为以下子类引入了标志Jekyll::Plugin为了使插件作者能够明确向 Jekyll 提供订购信息。当新的插件子类被实例化并按优先级排序Jekyll::Site被实例化。如果你想要你的cloudfoundry要运行的插件before or after另一个插件，您可以修改其优先级，以便在处理方面它将先于其他插件。

这仅对以下子类有效Jekyll::Plugin， 包括Jekyll::Converter and Jekyll::Generator。这就是为什么它适用于您的转换器，但不适用于您的Liquid::Tag– 液体标签没有优先级的概念，因为它们不竞争。

例如，以一个具有以下内容的网站为例：类别生成器插件 and a 站点地图插件。站点地图插件作者希望确保站点地图中存在任何生成的页面（所有内容都应该在站点地图中！），因此它设置priority :low。类别生成器插件作者可能希望确保它在任何其他生成器（例如站点地图生成器）之前运行，因此它设置priority :high。这可确保类别生成器插件在站点地图插件之前运行，以便编译后的站点地图中包含类别页面。

默认优先级是:normal。按优先级降序排列，有：

• :highest
• :high
• :normal
• :low
• :lowest