0.3.0-beta.0 release cut

[birkir]

Backlog

• Setup wizard
• Previews and cookies handler
• field-slice refactor (Union bug)
• field-asset refactor
• field-select refactor
• internal/external authorization
• persist session
• change password (ui)
• change email (ui)
• create user (ui+core)
• create schema (group name bug)
• changelog and docs

[birkir]

Changelog

• Accounts system that has built in support for two-factor, oauth, reset passwords, multiple emails and more.
• Powered by graphql-modules so internal and external can be used as separate modules, if you want to run them in separate machines for example.
• Switched from Sequelize/sequelize-typescript to TypeORM for more database drivers, ActiveRecord, dependency injection and more.
• All migrations now run automatically on bootstrap/runtime.
• Now using type-graphql for internal api. They integrate well with typeorm.
• All internal lists use relay connection now.
• Dataloader integration for internal findOne lookups.
• Refactored PrimeField interface for simpler usage.
• Auto generated api docs
• Discarded peerDependencies for fields and went with dependencies.
• Removed primecms cli (will add to a separate package)
• Renamed:
  • ContentEntry -> Document
  • ContentRelease -> Release
  • ContentType -> Schema
  • ContentTypeField -> SchemaField
• Schemas now have variant enum instead of flags (for template, slices etc)
• Removed algolia support for now, will add later (and accepting PR's)
• More advanced filters and sort on findAll. Now allows nested fields within groups.
• Ensures unique type names for GraphQL types.
• Introduced subscriptions, so the UI can be synchronously optimistic on schema changes.
• Better update system interface
• Renamed language to locale

[birkir]

I'll be making alpha.1 cut and have some kind of E2E test pass.

[agustif]

Hey @birkir great to see the changelog and what's coming up, about the Algolia Integration, I would love to make a PR/branch and try a stab at it. I've implemented it before in a few flavours and would love the challenge.

Do you have any guidelines on what it should accomplish, how you want to go about it, it might be a plugin/different npm package if it's not integrated by default?

Thanks for reading!