bkegley / luminate Goto Github PK

The marketing site will live at luminate.coffee (the app will move to app.luminate.coffee)

• create marketing gatsby project
• figure out some terrible design
• add Mailchimp email signups
• go live!

Authenticated users have scopes in the format operation:resource (eg. read:coffee).

I'm not entirely sure if auth checks should happen in the resolver or in the service. Resolver checks would look like the following:

listCoffees: async (parent, args, {services}) => {
      if (!hasScopes(['read:coffee']) throw new Error('Not authorized')
      return services.coffee.getConnectionResults(args)
    },

Mongoose Docs
Mongo Docs

This is a placeholder issue for me to dump current problems with Docker setup. I'll probably (most likely not) clean this up sometime.

Docker Volume Permissions

User mongo model should provide a method for updating the user that updates both user collection and organization.users.name

There are still some dangling dependencies fromtheme-ui eg @emotion/core that need to be removed

Currently, list query handlers (e.g. ListCoffeesQuery) return relay connection results in the form of:

{
  pageInfo: {
    hasNextPage: true,
    nextCursor: '1234',
    prevCursor: '5678'
  },
  edges: [
    {
      node: {...},
      cursor: '1357'
    }
  ]
}

This couples the query handler to its use as a specific GraphQL resolver which means we can't use any
of that logic as a field resolver any of that logic as a field resolver. Instead we should return an
array of aggregates.

CommandHandlers should implement an interface that extends ICommandHandler. This would help to keep types consistent when passing commands to the CommandRegistry for processing.

interface ICreateEntityCommandHandler extends ICommandHandler<CreateEntityCommand, Entity> {}

CommandRegistry.process<ICreateEntityCommandHandler>(....)

I can't really figure out why Variety/index.ts is having issues resolving without directly referencing it. Currently working but importing with .../Variety/index instead of just ../Variety

SCAA-Official-Cupping-Form.pdf
use SCA cupping form as initial template

A cupping session consists of multiple coffees which can be an individual roast or a specific lot/bag-of-coffee and can have multiple users logging scores against that cupping.

Coffees should be able to be made up of other coffees by percentages. Add components field to map percentages of coffees to a coffee.
e.g. BiitBlend (a coffee document) could be made up of 50% Guatemala (a coffee document) and 50% Ethiopia (a coffee document)

In a fresh install (and not running in Docker), depending on your local system, you may have issues building bcrypt. As a placeholder fix run sudo apt-get install -y build-essential python.

After migrating to nest we lost all of our hacky repo scoping logic. At the moment, we're just returning everything. We'll probably want to only return the results the user is authorized to view.

<Drawer> should trap focus to prevent tabbing into inputs that aren't within the drawer.