rahmatya685

# GraphQL Circular Dependencies

## Question

Imagine we have two entities: `Activity` and `Supplier`.
- Every activity can have a supplier
- Every supplier can have multiple activities

When defining the schema, `Activity` references `Supplier` and `Supplier` references `Activity` — creating a circular dependency. Is that an issue in GraphQL? What are the consequences and how do you resolve it?

rahmatya685

My Android Java Code Review Checklist

1. Is the functionality correct?
2. Are the classes named suitably?
3. Are the functions named suitably?
4. How's the datastructure being used? Is it the correct DS or it needs improvement?
5. Can the classes be further borken into small classes?
6. Do we need an interface?
7. If it contain functions that can be reused later then are there Utils created for them?
8. Can it use already available Util functions?
9. Does the large set of input for a function deserve a new bean to be created?

rahmatya685

New features and changes workflow guide

This guide describes what steps usually work best when adding new features to a product. The guidelines are not mandatory; simpler features may not need any of these steps. They exist to help battle the hardest new features to add :)

The steps are not necessarily in the correct order - this is the usual order. Going back to an older step to add/change things is okay.

Brainstorming sessions

Goal: collect all that we can come up with for the new feature or change. Everything goes into an unorganized document (wiki page). Possible ways to organize this document is into proposal items (and proposal detail item for each proposal item).

rahmatya685

git add .   ==> add All changes in current repo to staging directory
git log -n [count]  ==> get limited number of logs
git diff  ==> show changes of files in current repo versus worikng directory
git diff --staged or --cached   ==> show changes in current
 

undo working directory changes 
git checkout -- index.html   ==> replace current changes in this file with what we have in copy of this file in repository(latest commit)
  
--undoe staged changes