Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Migrate commonly used helper libraries to fluidproject organisation.

Description

Over the course of various grants, a few key helper libraries have been created that make it possible to do and/or test key things with Infusion. Now that the related grants are drawing to a close, it would be helpful to put these commonly-used libraries somewhere where a more active community can help maintain them.

Here is a list of packages that could potentially be migrated:

gpii-webdriver
gpii-express
gpii-glob
gpii-grunt-lint-all
gpii-grunt-mdjson-lint (collapsed into fluid-grunt-lint-all)
gpii-binder
gpii-diff
gpii-handlebars
gpii-json-schema
gpii-launcher
gpii-location-bar-relay
gpii-testem
gpii-pouchdb
gpii-mail-test (Required for gpii-express-user).
gpii-couchdb-test-harness

gpii-express-user Still having trouble getting CI working.

Of those, I have heard from people using gpii-binder frequently, and I know the linting infrastructure is heavily used. gpii-glob is required by gpii-grunt-lint-all, so that one probably also has to come.

I suspect gpii-handlebars might be used, and I have heard from individuals in the community using gpii-webdriver and gpii-launcher.

= done
= pull request in progress
= blocked

Environment

None

Activity

Show:

Justin Obara July 9, 2020 at 11:21 AM

 thanks for the info/update.

Tony Atkins [RtF] July 9, 2020 at 7:54 AM

Hi, Justin. The replacement used within the GPII is being migrated to fluid-couchdb-test-harness. The Fluid IoC test fixtures provided by that package can use a docker container, a Vagrant VM, or a standalone instance of CouchDB for local testing. I will likely set it up to use a docker container (which GitHub Actions supports) in CI.

However, I have been trying to think of less disruptive ways to move forward. I will look at the current state of affairs when attempting to migrate fluid-pouchdb. It may be that we have a third option, i.e. abandoning our fork of the pouchdb stack in favour of a newer version that already works with node@12.

Justin Obara July 8, 2020 at 9:15 PM

 what was the alternative you adopted for test in GPII? Did you just run a full instance of couchdb for it?

Tony Atkins [RtF] July 3, 2020 at 6:07 PM

To be honest, I did not have real plans to support gpii-pouchdb moving forwards, as it requires supporting a fork of several very old versions of the underlying libraries. The forks are required for non-browser (i.e. node) usage, but maybe we can remove the non-browser parts as part of the migration, and then it would at least be a good starting point for people who use it more often (and much easier to maintain in general).

Gregor Moss July 3, 2020 at 5:24 PM

I hope it all goes smoothly!

Here's what's currently used by the Storytelling Tool, for reference:

  • Directly

    • gpii-binder

    • gpii-grunt-lint-all

    • gpii-handlebars

    • gpii-location-bar-relay

    • gpii-pouchdb (used to mock CouchDB in browser tests)

  • Via other deps

    • gpii-express

    • gpii-glob

    • gpii-grunt-mdjson-lint

Fixed

Details

Assignee

Reporter

Priority

Created July 2, 2020 at 2:08 PM
Updated July 22, 2024 at 2:35 PM
Resolved July 7, 2020 at 12:14 PM