thebenforce / vscode-appsync-resolver-autocomplete

Adds autocomplete functionality to vscode when editing AWS AppSync resolver vtl files.

appsync-resolver-autocomplete README

Adds autocomplete support for AppSync resolver templates when editing .vtl files.

References

• Completions Sample
• Resolver Mapping Template Reference

vscode-appsync-resolver-autocomplete's Issues

Visual Studio Code MacOS

Hello,

I have installed the autocomplete tool in Visual Studio Code on Mac.

The autocomplete does not appear to function in the .vtl file. I was curious if there is any additional configuration to get this working for me.

I just added it from the Marketplace, but have not changed any other settings.

I have tried restarting VS Code.

Regards,

Basic Template Previews

Use VelocityJs to render a preview of the vtl file. This will only provide a view with realtime updates. No AppSync methods or context data will be available.

Please publish to the OpenVSX Registry

There are a growing set VSCode variations and other IDEs that use VSX extensions. Microsoft bars them from using Microsoft VSCode VSX Registry. The Eclipse Foundation hosts the OpenVSX Registry which enables people not using official VSCode or using other IDEs to use the extension. Please publish your excellent extension to the OpenVSX registry.

• How to publish to the OpenVSX Registry
• The OpenVSX extension repository

Thank you!

Preview Data

Allow users to define context data globally, and per workspace.

AppSync Methods

Implement appsync methods as part of the velocity context.

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

No vsce personal access token specified. (set env "VSCE_TOKEN")

Unfortunately this error doesn’t have any additional information. Feel free to kindly ask the author of the semantic-release-vsce plugin to add more helpful information.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

Feature Request: vtl tag

Hi!

It would be nice to be able to get the same code completion and syntax highlighting using a vtl tag on a template string like so:

// ts / js
const resolver = vtl`
#if($ctx.args.id)
  "true"
#else 
  "false"
#end
`;

I know this extension is for code completion only, but I'm assuming it uses the "velocity" language token / reference from another extension to be activated. Is it true?

I'm wondering what minimal work could be done in order to "enable" the language inside the string literal so both extensions would work.

Cheers!

EDIT:

How feasible is this?

package.json

    "contributions": {
      ...
      "grammar" : {
        "injectTo": [
          "source.js",
          "source.ts",
        ],
        "scopeName": "inline.velocity",
        "path": "./syntaxes/velocity.inline.json",
        "embeddedLanguages": {
          "meta.embedded.block.velocity": "velocity"
        }
      }
      ...

// syntaxes/velocity.inline.json

{
  "fileTypes": ["js", "ts"],
  "injectionSelector": "L:source -string -comment",
  "patterns": [
    {
      "name": "taggedTemplates",
      "contentName": "meta.embedded.block.velocity",
      "begin": "(`)(velocity|vtl)",
      "beginCaptures": {
        "1": {
          "name": "punctuation.definition.string.template.begin.js"
        },
        "2": {
          "name": "comment.line.velocity.js"
        }
      },
      "end": "`",
      "endCaptures": {
        "0": {
          "name": "punctuation.definition.string.template.end.js"
        }
      },
      "patterns": [
        { "include": "source.velocity" }
      ]
    }
  ],
  "scopeName": "inline.velocity"
}