Repository navigation
chore!: removes view-history permission - #33042
Conversation
|
Looks like this PR is ready to merge! 🎉 |
🦋 Changeset detectedLatest commit: 642d0c0 The changes in this PR will be included in the next version bump. This PR includes changesets to release 32 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## release-7.0.0 #33042 +/- ##
==============================================
Coverage 55.00% 55.00%
==============================================
Files 2596 2596
Lines 56003 56003
Branches 11589 11589
==============================================
Hits 30802 30802
Misses 22558 22558
Partials 2643 2643
Flags with carried forward coverage won't be shown. Click here to find out more. |
4cd82d5 to
ed431ca
Compare
|
ps: there is no need to remove all the i18n keys, if you removes the also the title should be |
Good to now, I wasn't sure about the i18n being auto removed if I removed only in en. |
| addMigration({ | ||
| version: 305, | ||
| async up() { | ||
| await Permissions.deleteOne({ _id: 'view-history' }); |
There was a problem hiding this comment.
The permissions collection has trash, wonder if we should skip the trash on this delete, like
Permissions.col.deleteOne({ _id: 'view-history' })
There was a problem hiding this comment.
Hey @KevLehman , can you elaborate? Not sure I understood what you meant.
There was a problem hiding this comment.
What i mean is that we have something called trash for some DB models. This copies the object before it's deleted into the trash, and then it removes from the original collection.
SO in this case, when removed like this, the permission will be in the trash. Not really sure that's a big concern but would be nice to ask if we can just skip the trash instead for this case.
There was a problem hiding this comment.
Got it.
@ggazzo , @matheusbsilva137 any thoughts on this?
Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>
Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>
Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>
Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>
Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>
Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>
Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>
Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>
Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>
Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>
Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>
Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>
Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>
Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>
Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>
Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>
Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>
Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>
Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>
Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>
Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>
Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>
Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>
Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>
Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>
Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>
Proposed changes (including videos or screenshots)
This PR aims to completely remove the
view-historypermission, since it has never been used since its creation. It also adds a migration to remove it from thepermissionscollection, and removes the i18n keys forview-historyandview-history-description.Issue(s)
CORE-605
Steps to test or reproduce
Further comments