Update package name and info

Author: Alireza Zamani

README.md

@@ -7,13 +7,13 @@ This package offers you a simple decorator to set cache control on your resolver
 On Yarn:
 
 ```shell
-yarn add @exonest/graphql-cache-control
+yarn add nestjs-gql-cache-control
 ```
 
 On NPM:
 
 ```shell
-npm install @exonest/graphql-cache-control
+npm install nestjs-gql-cache-control
 ```
 
 ## Usage
@@ -40,12 +40,13 @@ GraphQLModule.forRoot({
   ],
 }),
 ```
+
 > To add Redis or other caching stores, check [Apollo's docs](https://www.apollographql.com/docs/apollo-server/performance/caching/#in-memory-cache-setup)
 
 Then, you can use the decorator on your queries and field resolvers:
 
 ```ts
-import { CacheControl } from '@exonest/graphql-cache-control';
+import { CacheControl } from 'nestjs-gql-cache-control';
 
 @Resolver((type) => Post)
 export class PostResolver {
@@ -55,16 +56,16 @@ export class PostResolver {
     // database calls
     return posts;
   }
-  
+
   @ResolveField(() => User)
   @CacheControl({ inheritMaxAge: true })
   owner() {
     // database calls
     return owner;
   }
-  
+
   @ResolveField(() => boolean)
-  @CacheControl({ maxAge: 5, scope: "PRIVATE" })
+  @CacheControl({ maxAge: 5, scope: 'PRIVATE' })
   hasLiked() {
     // database calls
     return hasLiked;
@@ -75,15 +76,15 @@ export class PostResolver {
 ## How The Apollo Cache Works
 
 Please carefully read [Apollo's docs about caching](https://www.apollographql.com/docs/apollo-server/performance/caching/) to understand how caching works, since it has a set of rules for cache calculation. In a brief:
->a response should only be considered cacheable if every part of that response opts in to being cacheable. At the same time, we don't think developers should have to specify cache hints for every single field in their schema.
-So, we follow these heuristics:
-Root field resolvers are extremely likely to fetch data (because these fields have no parent), so we set their default maxAge to 0 to avoid automatically caching data that shouldn't be cached.
-Resolvers for other non-scalar fields (objects, interfaces, and unions) also commonly fetch data because they contain arbitrarily many fields. Consequently, we also set their default maxAge to 0.
-Resolvers for scalar, non-root fields rarely fetch data and instead usually populate data via the parent argument. Consequently, these fields inherit their default maxAge from their parent to reduce schema clutter.
 
+> a response should only be considered cacheable if every part of that response opts in to being cacheable. At the same time, we don't think developers should have to specify cache hints for every single field in their schema.
+> So, we follow these heuristics:
+> Root field resolvers are extremely likely to fetch data (because these fields have no parent), so we set their default maxAge to 0 to avoid automatically caching data that shouldn't be cached.
+> Resolvers for other non-scalar fields (objects, interfaces, and unions) also commonly fetch data because they contain arbitrarily many fields. Consequently, we also set their default maxAge to 0.
+> Resolvers for scalar, non-root fields rarely fetch data and instead usually populate data via the parent argument. Consequently, these fields inherit their default maxAge from their parent to reduce schema clutter.
 
 ## Connections (Pagination)
 
-If you happen to use [@exonest/graphql-connections](https://github.com/exonest/graphql-connections), `edges` and `node` will automatically inherit cache control from their parents. but otherwise you should set `inheritMaxAge` on your connection fields to prevent connections from cancelling your cache.
+If you happen to use [nestjs-gql-connections](https://github.com/overnested/nestjs-gql-connections), `edges` and `node` will automatically inherit cache control from their parents. but otherwise you should set `inheritMaxAge` on your connection fields to prevent connections from cancelling your cache.
 
 Why you should do that? because you probably don't want your connections to cancel your cache control. ([learn more](https://www.apollographql.com/docs/apollo-server/performance/caching/#default-maxage))

package.json

@@ -10,10 +10,10 @@
   "engines": {
     "node": ">=10"
   },
-  "homepage": "https://github.com/exonest",
+  "homepage": "https://github.com/overnested",
   "repository": {
     "type": "git",
-    "url": "https://github.com/exonest/graphql-connections"
+    "url": "https://github.com/overnested/nestjs-gql-connections"
   },
   "scripts": {
     "start": "tsdx watch",
@@ -36,8 +36,11 @@
     "singleQuote": true,
     "trailingComma": "es5"
   },
-  "name": "@exonest/graphql-cache-control",
-  "author": "Alireza Zamani",
+  "name": "nestjs-gql-cache-control",
+  "author": {
+    "email": "alirezazamani2922@gmail.com",
+    "name": "Alireza Zamani"
+  },
   "module": "dist/graphql-cache-control.esm.js",
   "size-limit": [
     {