diff --git a/.github/workflows/deployChrome.yml b/.github/workflows/deployChrome.yml
deleted file mode 100644
index 72cb034..0000000
--- a/.github/workflows/deployChrome.yml
+++ /dev/null
@@ -1,29 +0,0 @@
-name: Publish Chrome Extension
-on:
- push:
- branches:
- - OTHER
- # This will need to be changed - just making a random branch for now so that it doesn't flag the main branch
-
-jobs:
- build-and-publish:
- runs-on: ubuntu-latest
- steps:
- - uses: actions/checkout@v4
-
- - name: Setup Node.js
- uses: actions/setup-node@v4
- with:
- node-version: '20.7.0'
-
- - name: Install Dependencies
- run: cd package && npm ci
-
- - name: Build
- run: cd package && npm run build
-
- # https://developer.chrome.com/docs/webstore/using-api
- # Challenges:
- # Chrome Extensions go through a review so all changes to npm package need to be backward compatable because we can publish npm before the extension is approved and we don't know when the extension will be approved
- # Not clear if we zip it like we did when we uploaded it manually. When we uploaded it manually we zipped the dist folder and uploaded just that.
-
\ No newline at end of file
diff --git a/.github/workflows/npmPublish.yml b/.github/workflows/npmPublish.yml
deleted file mode 100644
index 5845320..0000000
--- a/.github/workflows/npmPublish.yml
+++ /dev/null
@@ -1,31 +0,0 @@
-name: Publish NPM Package
-
-on:
- push:
- branches:
- - main
-
-jobs:
- build-and-publish:
- runs-on: ubuntu-latest
- steps:
- - uses: actions/checkout@v4
-
- - name: Setup Node.js
- uses: actions/setup-node@v4
- with:
- node-version: '20.7.0'
- registry-url: 'https://registry.npmjs.org/'
-
- # Ideally we automatically update the version number in package.json
-
- - name: Install Dependencies
- run: cd package && npm ci
-
- - name: Build
- run: cd package && npm run build
-
- - name: Publish to NPM
- run: cd package && npm publish
- env:
- NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
diff --git a/README.md b/README.md
index b535c9e..9216de5 100644
--- a/README.md
+++ b/README.md
@@ -44,7 +44,7 @@ React Query Rewind introduces a powerful DevTool extension designed to work in c
_picture of importing the component_
```javascript
- import ReactQueryRewind from 'react-query-rewind';
+ import ReactQueryRewind from "react-query-rewind";
```
3. Place ReactQueryRewind next to the root of your application inside the QueryClientProvider component.
@@ -61,26 +61,26 @@ React Query Rewind introduces a powerful DevTool extension designed to work in c
4. Open the Chrome DevTool Extension and start coding!
-
+
# Features
- Query States: Upon opening RQRewind in Chrome Dev Tools, you will see the Queries tab open with a drop down menu listing the query keys of all the incoming queries. Select the queries that you want to monitor, make changes on the web app, and the changes of query states will be logged as reflected by the growing number above the play bar. Use the play bar to navigate to a particular state snapshot that you would like to inspect.
-
+
- State Diff: Toggle on the Diff button to see state changes between each snapshot highlighted. Turn on the switch on top of the page to show only parts of the state that are changed.
-
+
- Live UI Change: As you review the state change history, there is also the option to turn on the time travel mode by clicking on the clock icon button. Under time travel mode, when visiting a logged state snapshot on RQRewindl, the UI of the app will change accordingly. Turn off time travel mode for RQRewind to continue logging future state changes.
-
+
- Component Tree: Click on the Component Tree tab and turn on the Start Profiling switch. Click on any component on the app, and view the component tree that is rendered on the dev tools panel.
-
+ 
