weakky / prisma-ecommerce Goto Github PK

There are no payment view yet. This view would appear after the "Summary" step.
Integrating such a lib would be extremely sick https://github.com/sbycrosz/react-native-credit-card-input 🌮

Using graphql-shield or https://blog.graph.cool/graphql-directive-permissions-authorization-made-easy-54c076b5368e

Step1. Allow only users with role ADMIN to perform those mutations:

# Upsert mutations
  upsertBrand(brandId: ID, categoryId: ID!, name: String!): Brand
  upsertAttribute(attributeId: ID, categoryId: ID!, value: String!): Attribute
  upsertCategory(categoryId: ID, name: String!): Category
  upsertOption(optionId: ID, name: String!, values: [OptionValueInput!]!, categoryId: ID!): Option
  upsertProduct(
    productId: ID,
    name: String!,
    categoryId: ID!,
    brandId: ID!,
    available: Boolean!,
    optionIds: [ID!]!,
    variants: [ProductVariantInput!]!,
    attributesIds: [ID!]!,
    unavailableOptionsValuesIds: [ID!]!,
    displayPrice: Float!,
    imageUrl: String
  ): Product

  #Upsert Shop metadata
  upsertBestSalesProducts(shopMetadataId: ID, bestSalesProducts: [OrderableProductInput!]!): ShopMetadata!
  upsertNewProducts(shopMetadataId: ID, newProducts: [OrderableProductInput!]!): ShopMetadata!
  upsertMOTD(shopMetadataId: ID, MOTD: String!): ShopMetadata!

  # Delete mutations
  deleteProduct(productId: ID!): Product
  deleteOption(optionId: ID!): Option
  deleteBrand(brandId: ID!): Brand
  deleteAttribute(attributeId: ID!): Attribute
  deleteCategory(categoryId: ID!): Category

#Order mutations
  setOrderAsPrepared(orderId: ID!): Order #Can be updated only by admins (eg: to set order as prepared)

And those queries:

allCustomers: [User!]!

Send a query when clicking on the "Continue" button on the cart view, to perform a global check on all the items present on the user cart, to make sure every items are still available nor deleted.

Result should probably not be cached. Use fetchPolicy: 'network-only' here.

The MOTD field is already present in the datamodel.

Everything still needs to be done though, on Prisma (building the resolver), on the backoffice (creating the view to be able to update it), and on the mobile app (to query and display the MOTD)

The current UI's for those are really prototypes so that I could continue the RN app. They definitely needs to be done in a better way, mostly in terms of UI. The UX is already kind of good.

Provide a way to go back to the product list

They're just not present at all yet.

On the prisma side, an empty string is set for now.

When a client submit an order:

• Send him a mail with a detailed invoice of his order

For the seller:

• Allow him to generate a daily/monthly receipt of all the orders processed, for accounting reasons

Allow the developer to...

• Configure his development environment
• Install projects
• Launch projects
• Reset projects (npm cache, watchman, node_modules..)
• Debug projects (display dependancies, track errors..)

Although there's already some pagination handled by react-table (UI wise), we're querying all the products at once, which will lead to really slow performance in the future.

• React
• React Native
• Prisma
• GraphQL Bindings

I need this file to test with data, but I can't find it anywhere.

Find a way to build cleaner and more maintainable forms for every models that are CRUD using the backoffice

Hint: This might be an option https://github.com/Volst/graphql-form-helpers

• In the cart
• In the order list

The button is present, but nothing is done yet.

react-native-picker should be used, just like on the <Product /> view.

Bonjour Flavian, je suis très intéressé par ce repo et le code que tu développes, moi même je travaille avec Prisma,
Je t'ai contacté sur twitter récemment, pourrai-tu m'appeler sur mon tel au 0675505209?. Je cherche quelqu'un comme toi.
Tu peux fermer cette issue après l'avoir lue

Inline-styles should be put in their respectives .styles.js files.

Using styled-components could be an option as well

https://github.com/Microsoft/react-native-code-push

As the app will solely be used as a "drive" e-commerce system, we need a way to be able to see incoming orders easily.

An iPad app sticked to a wall, plugged to the prisma API with subscriptions to get in-real incoming orders would be the perfect option.

This app would allow the shop owner to:

• See incoming orders
  • Filter them by "orders to prepare" / "orders prepared"
  • Set them as prepared (to notify the user)
• Easily change variants availabilities of products

All the views are made, but the mutation is not yet sent to the server.

When a product is deleted from the backoffice, we delete all cart items that had this product in it.

When the user logs in again, we should warn him we an Alert.alert() that some products of his cart were deleted.

Solution:

We could simply save in AsyncStorage the number of item in his cart, then compare it when fetching his cart from the server.

If localCartItemsLength < serverCartItemLengths then Alert.alert() the user.

An example of a problem: select a product on the home page, then once on the product sheet, and go back.

The last tab on the RN app will be dedicated to user's account, allowing him to manage all kind of stuff.

• List his orders (with ability to add an order to the cart)
• Edit his account information
• Grab shops information (opening hours, address, etc etc. This may be put in the ShopMetadata model)
• Allow to change his shop
• Logout
• Terms of Service
• More ideas ?

Users are redirected to home view right away after successful payment.

There should be an intermediate view confirming that his payment was successful.

Provide a way for users to be able to reset their passwords.

An email should be sent.

As of now, when adding options to a product, you're forced to use ALL the linked options values. There should be a way to only add SOME of the values.

eg: A t-shirt can only exist in Color blue, and black, even though the Color option has the color value yellow. In this case, admin should be able to disabled option value yellow.

I'm currently working on your project.

did update apollo and code relative to work with last version.
app working with last apollo2 now.
I already setup the Facebook login with prisma in my repo, i can add it here too

Only the name of the product is shown for the moment.

We could only show the optionValues.

t-shirt x 2 (XL, Blue)

Prevent submitting forms when required fields are not fullfilled.

(Especially the product creation/edition form)

When a product was put in an order, it cannot be deleted.

GraphQL error: The change you are trying to make would violate the required relation '_OrderLineItemToVariant' between OrderLineItem and Variant

• Provide a way to send push notifications from the backoffice
• Push a notification when an order status is set to PREPARED