Add co-author to existing package (Update e.json)

[axemonk]

Added co-author @michaelblyons

• 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").

My package is an existing package adding support for syntax highlighting for Excel formulas (with aspirational support for GSheets and others).

There are no packages like it in Package Control.

[packagecontrol-bot]

Automated testing result: SUCCESS

Packages modified:
  - Excel formula

[michaelblyons]

I endorse this. I'm not sure if that was clear.

@axemonk You may want to edit the PR title to say that the change just adds a co-author to Excel formula.

[axemonk]

thanks for the heads up @michaelblyons. Done.

[axemonk]

Update: eventually we will want to rename this package to be "Spreadsheet formula" instead of "Excel formula" (it now supports spreadsheet applications other than just Excel), with "Excel formula" being added to the "previous_names" key instead. Since that will change the proper position of this package in the Package Control repository according to alphabetization, I'm not sure what the best way to go about that is (should I close this pull request before reopening it with both the original change and the move/rename committed instead?). Please let me know if you have any specific guidance. Thanks.

[braver]

Since that will change the proper position of this package in the Package Control repository according to alphabetization

A package's name is its unique identifier. If you rename a package, move the entry to the new alphabetical position (ie. delete the old one, create a new one). The "previous_names" key will ensure package control knows to treat it as the same package as before but under a different name.

should I close this pull request before reopening it with both the original change and the move/rename committed instead?

Yes please.