[DRAFT] Custom decoders

[shahm5]

A very rough draft POC of custom message decoding using Protobuf (#383) https://protobufjs.github.io/protobuf.js/index.html

Some next steps

• indication that a decoder has been created on "save"
• error catching/handling
• styling the proto file/type selection form

• save uploaded files or Types in local storage

  This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Thank you for contributing to the Azure IoT Explorer!

This checklist is used to make sure that common guidelines for a pull request are followed.

General Guidelines

• [ ] If introducing new functionality or modified behavior, are they backed by unit tests?
• [ ] Have all unit tests passed locally? (by running npm run test command)
• [ ] Have you updated the README.md with new screenshots if significant changes have been made?
• [ ] Have you update the package version if the current version in package.json is not higher than the version released?

[shahm5]

Sample .proto file (the corresponding type would be testpackage.TestMessage)

package testpackage;
syntax = "proto3";

message TestMessage {
    string test_field = 1; // becomes testField
}

Sample message encoded using this file new Message(new Buffer([10,13,65,119,101,115,111,109,101,83,116,114,105,110,103]));

Decodes as

{
    "testField": "AwesomeString"
}

[YingXue]

Elsie is updating the pr to make it to production