Update cache-store on routes listing
What problem is this solving?
When an app route is edited and there isn't a user route for the specific binding, a new one is created.
The idea here is to update the cache-store, replacing the default app route with the user route created.
How should this be manually tested?
Screenshots or example usage
Type of changes
| ✔️ | Type of Change |
|---|---|
| ✔️ | Bug fix |
| _ | New feature |
| _ | Breaking change |
| _ | Technical improvements |
Notes
Depends on pages-graphql
Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖
Please select which version do you want to release:
-
[x] Patch (backwards-compatible bug fixes)
-
[ ] Minor (backwards-compatible functionality)
-
[ ] Major (incompatible API changes)
And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.
- [ ] No thanks, I would rather do it manually 😞
Beep boop :robot:
I noticed you didn't make any changes at the docs/ folder
- [x] There's nothing new to document :thinking:
- [ ] I'll do it later :disappointed:
In order to keep track, I'll create an issue if you decide now is not a good time
- [ ] I just updated :tada::tada: