sillsdev / appbuilder-portal Goto Github PK

There is still a need for distributing Electron-based apps for desktop in situations where PWA install is not an option.

Nativefier can generate an Electron app based on a website (http or file url). It uses electron-packager to create the Windows, Mac, or Linux application folder. There are several options for creating a distributable.

For Linux, we should look at snap or flatpak.

For Mac, it should be notarized. We can look at using Circle CI to run macOS tasks remotely. We have done research with appbuilder-ci-ios to sign iOS apps remotely. Something similar should be doable with Notarization.

It seem's you're using use-redux in your dependency.

As react-redux now support hooks, you should switch to react-redux for the official react redux support.

use-redux will be deprecated soon and the repository will be archived.

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Location: renovate.json
Error type: Invalid JSON (parsing failed)
Message: Syntax error: expecting String near // Up

65kb: https://bundlephobia.com/[email protected]
89kb: https://bundlephobia.com/[email protected]
Total: 154kb

6.5kb: https://bundlephobia.com/[email protected]
29kb: https://bundlephobia.com/[email protected]
Total: 35.5kb

date-fns is over one order of magnitude smaller, and supports (currently) 46 locales.
https://date-fns.org/

brief comparison from 2016: date-fns/date-fns#275 (comment)

This issue contains a list of Renovate updates and their statuses.

Rate Limited

These updates are currently rate limited. Click on a checkbox below to force their creation now.

• Update dependency source-map-loader to v1
• Update dependency style-loader to v1
• Update dependency ts-loader to v8
• Update dependency ts-node to v9
• Update dependency tslint to v6
• Update dependency typescript to v4
• Update dependency url-loader to v4
• Update dependency use-debounce to v3
• Update dependency uuid to v8
• Update dependency webpack-node-externals to v2
• Update mui monorepo (major) (@material-ui/core, @material-ui/icons)

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update Node.js
• Update XUnit packages (xunit, xunit.runner.visualstudio)
• Update dependency @bigtest/interactor to v0.15.0
• Update dependency dotenv.net to v1.0.6
• Update microsoft/dotnet Docker tag
• Update nginx Docker tag to v1.19.2
• Update TypeScript type definitions (major) (@types/mocha, @types/pollyjs__adapter, @types/pollyjs__core, @types/react-router-dom, @types/sinon, @typescript-eslint/eslint-plugin, @typescript-eslint/parser)
• Update dependency copy-webpack-plugin to v6
• Update dependency dotenv.net to v2
• Update dependency eslint to v7
• Update dependency eslint-config-prettier to v6
• Update dependency html-webpack-plugin to v4
• Update dependency karma-typescript to v5
• Update dependency prettier to v2
• Update dependency react-redux to v7
• Update dependency react-toastify to v6
• Update dependency react-use to v15
• Update dependency sass-loader to v10
• Update dependency semantic-ui-react to v1
• Update dependency sinon to v9
• Check this option to rebase all the above open PRs at once

• Check this box to trigger a request for Renovate to run again on this repository

The current on boarding process:

1. Organizational Admin invites user to organization with email by

   a. clicking "+ Invite User"
   

   b. entering email in popup

2. User receives an email

With this link:
https://dev.scriptoria.io/invitations/organization-membership/ef645de4-8b47-4bcd-a61a-d56a7b110aa4

3. User clicks on link in email and goes to for with Log In or Sign Up. Which should they use?

4. Use Sign up then get "Please verify your email address"

5. Receive "verify your account" from "[email protected]" ? (this might be due to this being the dev tennant)

6. Receive "Email verification" screen

7. Sign out and try to sign in ... but get "Organization Membership is Required

Who is Organization administrator? How do I contact them?

8. Finally check with Organization Admin, but there is no record of the user being added to the organization.

9. Try link in first email and Sign In this time

10. Sign out, wait a little, sign in again and l get logged in, but I can't do anything:

11. Communicate to Organization Admin again ... they can now see the user and assign to groups and roles

Observations

• Email from Scriptoria is poorly formatted (simplistic). Should we make it more like email coming from Auth0?
• Why didn't the first time with the invitations/organization-membership and the Signup not connect the new user to the organization?
• Sometimes when the user tries to use the invitation for the first time, they get a "token already used" (I think React has rendered multiple times and sends multiple requests).
• It would be good for the admin to assign roles and group at the time of the invitation (it would require changing the schema for the OrganizationMembership.

We will be switch the front-end and back-end of the website to Svelte/SvelteKit. One of the reasons is that the performance of the project page is unpredictable and often times out. We used to have a 5 second timeout and then would stop rendering the page. We had to increase it to 10 seconds and then 60 seconds.

The Project page has several related objects in the query:

• Products of Project
• Groups of Organization of Project
• Users in Group of Project
• Authors in Group of Project
• ProductTransition of Product
• ProductDefinitions of Organization

The Project page has these separate components:

• Project Details
• Project Dropdown
• Products List
• Product Summary
• Product Dropdown
• Organization
• Project Owner (User List)
• Project Group
• Authors
• Add Author
• Reviewers
• Add Reviewer
• Repository Location
• Settings

The project page has these dialogs:

• Product Details
• Product Publishing Properties
• Add Products
• Remove Products
• Product Details

The Project page has these related pages:

• Edit Project Details
• Product Files

Screenshots

Project Page

Project Dropdown

Product Dropdown

Project Owner

Project Group

Add Author

Add Reviewer

Product Details

Add Products

Remove Products

https://support.crowdin.com/in-context-localization/

^ This needs to be embedded in the app.
It can be lazy loaded as to not affect the initial load time.

Scriptoria uses DWKit .NET-based workflow engine to implement long-lived workflows. We chose this for the following reasons:

1. Our back-end was going to be ASP.NET Core
2. We wanted to allow the service to be run by non-programmers. So we wanted:
   a. no-code solution
   b. graphical workflow creation
   c. form engine
   Originally, the licensing cost of DWKit started at $3K/yr and has increased to $15/yr.

Here are reasons for changing the workflow:

• The license maintenance cost is too much.
• The handing of the service over to non-programmers never happened and will probably never happen.
• When we selected DWKit, we were not web developers and we were concerned with implementing the workflow forms. We are now more experienced web developers and it isn't a problem.
• We are using Svelte+SvelteKit for other web-based projects and it would be easier to maintain Scriptoria with Svelte+SvelteKit instead of React.
• Upgrading the version of the workflow engine is hard due to manual database migration for features we don't use.
• The version of DotNet Core we are currently using is very old (2.1). Upgrading to newer versions is a time consuming process.
• There are also dependent core libraries (for jsonapi) that have significant breaking changes for 2.1 to newer DotNet Core versions.
• Even with the graphical workflow, we still had to add code for the events.
• The workflows haven't changed and will only have minor changed (e.g. for auto rebuilds).
• Hosting the workflow in the back-end causes problems with the back-end crashes or needs to be restarted.
• The workflows can stall due to retry loops in the workflow stopping.

Plan:

• We will be implementing the workflow forms in Svelte+SvelteKit.
• We will be implementing the workflows in AWS Simple Workflow Service or AWS Step Functions

Did a bundle analysis from this branch/pr: #182

Main notes:

• (173KB gz) auth0-lock includes its own node_modules|
  • 72KB is "node_modules"
  • 101KB is "lib" -- maybe there is a way to get this trimmed down or load auth0-lock async when we hit the login route
• (132KB gz) semantic-ui
  • about 28KB is unused image assets
• (62KB gz) semantic-ui-react
  • should be able to be trimmed down by not importing any components from semantic-ui-react
• (62KB + 16.34KB + 24.85KB gz) moment
  • maybe look in to alternatives: https://blog.bitsrc.io/9-javascript-date-time-libraries-for-2018-12d82f37872d
• app.js is looking good at 63KB
  • 10KB is css - maybe this could be trimmed?

We will add a setting to a project that will cause it to initiate a rebuild workflow when a new version of App Builders is enabled on Scriptoria. When the rebuild is initiated, it will either:

• run rebuild workflow and stop at Verify and Publish step and notify reviewers when ready
• run rebuild workflow completely and notify reviewers of publication

Notifications will ignore user's preference of whether to receive notifications by email.

There will be an additional page in the admin pages to initiate a new rebuild.

The rebuilds should be only be initiated for projects that have completed the initial workflow and are not in the middle of a rebuild or republish workflow.

We need to decide if the rebuilds happen to all products of a project or whether we have to opt-in to auto rebuilds per product.

In the Android App to Google Play workflows, we used it have the user upload the APK during the Create App Store Entry step and then we would upload it again during Product Publish step. There was a recent change in the Google Play Store APIs that would fail the publish if we tried to upload the APK again. So we had to add logic in the workflow to only upload once.

For apps that are already in the store and they are being added to Scriptoria, we need to skip the Create App Store Entry and upload the APK during Product Publish.

I recommend that we add an option somewhere to specify whether the app already exists. This probably should be at Create App Store Entry.