Skip to content

Conversation

@tanben
Copy link

@tanben tanben commented Jun 26, 2019

@tourdedave
Copy link

Amazing!

We can't make this part of our standard library since the tool needs to stay vendor neutral. But we can make it so this PR can be wrapped inside of a SIDE plugin.

There's a little bit of work on our end to set up the infrastructure for it, but I think we can get that sorted pretty quickly (e.g., I can start on it next week) and post details here soon.

What this means from the user's perspective:

  • they would need to install a plugin (e.g., another web extension)
  • once installed, your exporter would be listed alongside all of the other available languages and work just like them

What this means from NewRelic's perspective:

  • you will need to refactor your code to work with the SIDE plugins API & a SIDE utils package (which I'll publish next week)
  • you will need to build/publish a web extension (either hosting it on your own or through the Chrome & Firefox web stores)

You can message me directly on the IRC or Slack Selenium channel (tourdedave) to talk about the details offline. See Join The Community on the SIDE help page for details on how to connect.

tourdedave pushed a commit that referenced this pull request Jun 30, 2019
…ch will be a public package. Placed the code-export specific bits behind `codeExport` so it can be destructured.
@tourdedave
Copy link

tourdedave commented Jul 1, 2019

Okay, here's what I've done:

  1. Published the utility code for code-export to npm under the package @seleniumhq/side-utils

  2. Made it so plugins can provide new languages for code export. Here's a link to the relevant docs.

To get started with writing a plugin, take a look at the Plugin docs. Also, you can see an example of how another vendor has created a Selenium IDE plugin here.

@tanben tanben closed this Jul 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants