Add FabricEngine Package

[zamadatix]

Add FabricEngine package repository definition in f.json

• I'm the package's author and/or maintainer.
• I have have read [the docs][1].
• I have tagged a release with a [semver][2] version number.
• My package repo has a description and a README describing what it's for and how to use it.
• My package doesn't add context menu entries.
• My package doesn't add key bindings.
• Any commands are available via the command palette.
• Preferences and keybindings (if any) are listed in the menu and the command palette, and open in split view.
• If my package is a syntax it doesn't also add a color scheme.
• If my package is a syntax it is named after the language it supports (without suffixes like "syntax" or "highlighting").
• I use [.gitattributes][3] to exclude files from the package: images, test files, sublime-project/workspace.

My package is similar to some other switch config file syntax highlighting packages for other networking vendors but is unique in that it supports the specific syntax of the Extreme FabricEngine switch platform, which is incompatible with other syntax definitions.

Note: The repo name is more generic but overridden so the package name is set to just "FabricEngine" per the naming guidelines.

[packagecontrol-bot]

Automated testing result: WARNING

Repo link: FabricEngine
Results help

Packages added:
  - FabricEngine

Processing package "FabricEngine"
  - WARNING: '.sublime-syntax' support has been added in build 3092 and there is no '.tmLanguage' fallback file
    - File: FabricEngine.sublime-syntax

[braver]

Please have a look at the Scope Naming and examples. Your main scope should probably be source.fabricengine (to enable features for source code, not plain text which would be enabled by text.fabricengine), and each other scope should end with .fabricengine to allow features to target your syntax specifically (e.g. variable.language.fabricengine.

[zamadatix]

Please have a look at the Scope Naming and examples. Your main scope should probably be source.fabricengine (to enable features for source code, not plain text which would be enabled by text.fabricengine), and each other scope should end with .fabricengine to allow features to target your syntax specifically (e.g. variable.language.fabricengine.

Thanks for the tip! I've cleaned that up a bit, hopefully it looks a bit more correct now.

[packagecontrol-bot]

Automated testing result: WARNING

Repo link: FabricEngine
Results help

Packages added:
  - FabricEngine

Processing package "FabricEngine"
  - WARNING: '.sublime-syntax' support has been added in build 3092 and there is no '.tmLanguage' fallback file
    - File: FabricEngine.sublime-syntax