This project is out of date and should include the generic babel preset

https://github.com/bdougie/open-sauced/blob/master/package.json#L11

These queries are deprecated and no longer used by the project.

• remove references in any files
• remove files

What is the current behavior?

This project is calling data.refetch. This should instead be a subscription.

If the current behavior is a bug, please provide the steps to reproduce.

Graphcool has subscriptions as a feature, it would be best to leverage that by adding a subscription to the ApolloClient

- What is the current behavior?
The current nav has an icon to create an issue. I would like to see a tooltip when I hover over the link.

- What is the expected behavior?
I am intrigued by this library react-simple-tooltip, but feel this should be done in just simple css and js.

- Do you want to request a feature or report a bug?
Bug

- What is the current behavior?
When I add a new repo to this GraphQL database using the mutation it redirects to the home page but the data does not refetch. I have to do a hard refresh to get it to work.

- If the current behavior is a bug, please provide the steps to reproduce.

1. visit open-sauced.netlify.com
2. Click add new repo, enter a repo url, and click submit
3. Note the repo is note in the list
4. Hard refresh the page and note that the repo is now in the list

- What is the expected behavior?
The repo list should refresh when the component mounts.

I might try subscriptions or something similar to the refetch in apollo-client api

- Please mention your node.js, and operating system version.
React Router v4.1.1
Apollo v 1.2.0

https://github.com/apollographql/apollo-client-devtools

Not sure where this should go, but adding the link above should be good enough.

ok

test

- Do you want to request a feature or report a bug?
Feature
- What is the current behavior?
Currently, the content is fetched everytime the page loads. I originally started adding Redux to cache with Apollo but it was a pain to integrate and was not worth the effort. Apollo 2.0 has caching, which seems more ideal.

- What is the expected behavior?
Refresh the page and not rerender the content.

I am open to all things, just want to try out adding Styled Components now and see how it goes.

• Buttons
• Text styling, i.e. HeaderText or Subtext components.
• Form Styling components
• Grid/Layout

Potential security issue. localStorage is not protected by SSL encryption, My suggestion is to use a cookie, or react-cookies.

More info how to use react-cookies can be found in my blog post.

Evaluate:

• chakra-ui
• prime/components

- Do you want to request a feature or report a bug?
Feature
Instead of manually adding GitHub repos that a user is interested in following, Open Sauced could instead utilize a users' starred repos to populate their tracked repo list.

This would likely need to be prefaced with Github authentication.

Do you want to request a feature or report a bug?

What is the current behavior?

If the current behavior is a bug, please provide the steps to reproduce.

Please mention your node.js, and operating system version.**

What is the expected behavior?

Dependabot can't resolve your JavaScript dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Error whilst updating dependencies in package-lock.json:
Cannot read property 'match' of undefined

It looks like your lockfile has some corrupt entries with missing versions and needs to be re-generated.
You'll need to remove package-lock.json and node_modules before you run npm install.

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

You can mention @dependabot in the comments below to contact the Dependabot team.

Currently, data is being saved to the same user, need to save individual data separately.

Everything is on one single page. I need to add a router and create new pages. Might want to address a new file structure as well.

The Landing for opensauced.pizza needs a better experience. Open to suggestions

Is there a programmatic way to add Netlify deploy preview to the OneGraph whitelist and remove.

Perhaps a GitHub Action?

Things to look into

• Does OneGraph have an open API
• Can a netlify webhook trigger the OneGraph API

Do you want to request a feature or report a bug?

bug

What is the current behavior?

The README link for creating the schema is throwing errors due to a new breaking change: https://www.graph.cool/forum/t/introducing-the-model-directive/1272

If the current behavior is a bug, please provide the steps to reproduce.

Click the link to create a new graphql schema.

What is the expected behavior?

Clicking a link should create a new graphql schema on graphcool

this way the user will not worry where the data is saved and the app can run in debug without signing up for graph.cool making contributing a little bit easier 😄

It might make sense to look into graphql-auth to work with the identity authentication layer. I am not sure how it works, but opening up this issue as a reminder to research this.

https://github.com/kkemple/graphql-auth

Do you want to request a feature or report a bug?

Feature

What is the current behavior?

At the moment an old version of prisma(graphcool) is being used to save data and interact with Apollo. All of the above is out of and needs to be update.

What is the expected behavior?

• Update Apollo
• Update Prisma or move to another solution
• Identify schema for the following
  • ContributorBreadcrumbs (model to store key repo info)
  • Saved Repos
    • Save notes for saved repos (Wiki - should these be public?)

- Do you want to request a feature or report a bug?
This would be an enhancement to the current state of the app. I just found out about this project https://feathericons.com and think it would be great to add.

At the moment the goalId is being set in localStorage. This might grow into an issue, but for now it works. Redux or MobX seems like overkill for now, since this and the auth jwt is the only info being store globally.

Looking for a better way or confirmation

  _handleGoalId(id) {
    localStorage.setItem("goalsId", id);
  }

Questions

1. Should the be stored in a global store?
2. Is there other localStorage use in the future?

- Do you want to request a feature or report a bug?
Feature

- What is the current behavior?
Currently the code linting is forced using lint-staged. I am proposing replacing it with prettier instead.

- What is the expected behavior?
Instead of failing commits when lint fails, it would be nice to enforce linting on save.

I like testing and should test my components.

This is a note to myself to look into http://webpackmonitor.com/

https://dev-blog.apollodata.com/graphql-schema-stitching-8af23354ac37

There is a note to remove this when upgrading to webpack 5.

// [config/webpack.config.js](https://github.com/bdougie/open-sauced/blob/master/config/webpack.config.js#L160)
 filename: isEnvProduction
        ? 'static/js/[name].[contenthash:8].js'
        : isEnvDevelopment && 'static/js/bundle.js',
      // TODO: remove this when upgrading to webpack 5
      futureEmitAssets: true,
      // There are also additional JS chunk files if you use code splitting.

It is not clear what this is.

• Figure out the reference to this
• upgrade to webpack 5
• remove this

ok

- Do you want to request a feature or report a bug?
Feature
Given that this project circulates around GitHub projects, I think that a user should be able to authenticate and sign in with their GitHub account.

My understanding currently is that each user has their own version of Open Sauced hosted on something like Netlify, but there isn't anything in place to prevent someone else from adding repositories or comments to another user's list.
Adding GitHub authentication would protect users from potential vandalism or accidental editing of OpenSauce lists and also could open the doors to other interesting integrations with GitHub's API, such as grabbing 'starred' repos, etc.

hello

hello repo

hello repo

Graphcool has since change to Prisma and then again to subsequent version. I need to remove it, for now, to work on getting this project stable.

• Swap out Graphcool repo list with GitHub forks or stars related #32
• simplify new repo form to either clone or fork a repo
• explore if mirroring repository and issues is a valuable way to store data, similar to how https://www.onegraph.com/changelog works related #117

Add dependabot to get rid of security vulnerabilities

- Do you want to request a feature or report a bug?
Feature

- What is the current behavior?
currently, the only feature is adding notes to repos.

- What is the expected behavior?
Ideally a user should be able to search open issues on the repo using the GraphQL api and makes notes on it's content

- Do you want to request a feature or report a bug?
Feature

- What is the current behavior?
You save as many repositories as you would like, but you have no way to delete any.

- What is the expected behavior?
A simple delete button and button to remove repositories is needed

related to https://github.com/bdougie/open-sauced/issues/117

Also update or remove prisma. I am considering shoving everything into Onegraph, but would like to avoid vendor lockin. I need to look into the extent of that product.

Do you want to request a feature or report a bug?

enhancement/bug

What is the current behavior?

When upgrading webpack, there are multiple failures. The cli is not helpful due to breaking changes between 1.x to 4.0.0.

If the current behavior is a bug, please provide the steps to reproduce.

npm install -D @webpack/migrate
webpack-cli migrate config/webpack.dev.js

This will not work

What is the expected behavior?

I will need to upgrade manually, first to 2.x, then to 3.x, then 4.x

Opening this issue to track this upgrade.

I am thing a siracha or ketchup bottle, but open to suggestions. If you would like to take this, SVG would be needed, as well as a favicon.

1. Implement codecov or similar
2. Write test that cover state and logic in all components.

API mocking needed:

• AddRepoForm
• Issues.js
• Repositories.js
• Repository.js
• Goals

List of simple components

• Login.js
• Issues.js
• NoteForm.js
• AddRepoForm.js
• Header.js
• Footer.js
• Card.js
• RepoListItem
• ListGoals
• Instructions
• DashboardFooter
• CreateGoals

This project started in 2017, when Class components were fading as the premier way to create React Components.

This app needs consistency in its approach to Component development and will need to adjust to using hooks. This will improve consistency in how we leverage the apiGraphql.js file throughout the project.

TODO:

• remove use of compose HOC in favor of hooks
• update eslint rules to align with this change.

List of Containers components

• Dropdown.js
• Issues.js
• NewRepo.js
• NewRepoForm.js
• NoteForm.js
• Repositories.js
• Repository.js
• Login.js

List of Dumb components

• Header.js
• Footer.js
• Count.js

remove link from handle until a profile page is created

1. fetch goal data when repo mounts.

I broke the app, by regenerating my GitHub GraphQL. I just need to add the env vars to webpack definePlugin and such. I might also want to move my Apollo url there as well.

Storybook is an interactive development & testing environment for React components https://storybook.js.org

Do you want to request a feature or report a bug?

feature/bug

What is the current behavior?

At the moment GitHub Login does not. I am looking into creating an Oauth App to handle the authentication

If the current behavior is a bug, please provide the steps to reproduce.

Open the home page and see login is broken

What is the expected behavior?

I expect the login to work. Looking into to using one of the following solutions.

https://www.onegraph.com/docs/logging_users_in_and_out.html

or

https://github.com/checkr/react-github-login