Daniel (dB.) Doubrovkine

[Catch All Triage - [1](https://github.com/andrross), [2](https://github.com/dblock), [3](https://github.com/AmiStrn), [4](https://github.com/reta), [5](https://github.com/finnegancarroll)]

Try `document.createTextNode('XYZ')` to pass in? This worked for me: ```js gmail.tools.add_toolbar_button(document.createTextNode('XYZ'), (domEmail) => { ... }, 'asa'); ```

For Postman see https://learning.postman.com/docs/getting-started/importing-and-exporting/importing-and-exporting-overview/#importing-data-into-postman. Would take a PR that generates postman-compatible output that can be loaded directly.

[[Catch All Triage](https://github.com/opensearch-project/.github/blob/main/TRIAGING.md) - [1](https://github.com/dblock), [2](https://github.com/andrross/), [3](https://github.com/reta), [4](https://github.com/gaiksaya), [5](https://github.com/krisfreedain), [6](https://github.com/acarbonetto)]

Looks like it fixed itself, but is concerning.

cc: @andrross @amberzsy

@philiplhchan I think you're saying we need to generate proto files for a given API version. This can be done by first generating a version specific API (`npm run merge...

> a) can we follow same format here? easier to parsing. Yes. We would want a linter to fail when something inconsistent is used, also @nhtruong might have an opinion...

> Should we want to group into few proto files? To me what's important is to organize the source code that is written by humans well. But these are machine...

@vamshin @sean-zheng-amazon @jmazanec15 @model-collapse @navneet1v @zane-neo @ylwu-amzn @jngz-es @heemin32 @junqiu-lei @martin-gaievski @naveentatikonda @VijayanB @vibrantvarun @zhichao-aws