Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[popup] Platform Events links are not correct #500

Closed
2 tasks done
tprouvot opened this issue Jul 22, 2024 · 0 comments
Closed
2 tasks done

[popup] Platform Events links are not correct #500

tprouvot opened this issue Jul 22, 2024 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@tprouvot
Copy link
Owner

Make sure to read the troubleshooting section before creating an issue

  • I've read the common issues and the one I'm about to create is not one of those documented.
  • I've read the release note and the one I'm about to create is not already fixed.

Describe the bug
When selecting a platform event object in the popup object tab, the links (object name and fields) are incorrect
RecordType and Object List links are not relevant for this king of object, we don't have to display it.

Example for Object link::

  • 👎 /lightning/setup/ObjectManager/PurgeSObjectBatch__e/Details/view
  • 👍 /lightning/setup/EventObjects/page?address=%2F01IAW000004yaBB%3Fsetupid%3DEventObjects

To Reproduce
Steps to reproduce the behavior:

  1. Go to Object tab from the popup
  2. Type a platform event object name
  3. Click on the object name link
  4. Wrong url

Expected behavior
Url should redirect to the platform event setup page

Screenshots

image

Desktop (please complete the following information):

  • Version 1.24
@tprouvot tprouvot added bug Something isn't working help wanted You can work on this issue if you want to ! labels Jul 22, 2024
@tprouvot tprouvot self-assigned this Jul 22, 2024
@tprouvot tprouvot removed the help wanted You can work on this issue if you want to ! label Aug 2, 2024
tprouvot added a commit that referenced this issue Aug 2, 2024
## Describe your changes

## Issue ticket number and link
Closes #500 

## Checklist before requesting a review
- [x] I have read and understand the [Contributions
section](https://github.com/tprouvot/Salesforce-Inspector-reloaded#contributions)
- [x] Target branch is releaseCandidate and not master
- [x] I have performed a self-review of my code
- [x] I ran the [unit
tests](https://github.com/tprouvot/Salesforce-Inspector-reloaded#unit-tests)
and my PR does not break any tests
- [x] I documented the changes I've made on the
[CHANGES.md](https://github.com/tprouvot/Salesforce-Inspector-reloaded/blob/master/CHANGES.md)
and followed actual conventions
- [ ] I added a new section on
[how-to.md](https://github.com/tprouvot/Salesforce-Inspector-reloaded/blob/master/docs/how-to.md)
(optional)
@tprouvot tprouvot closed this as completed Aug 2, 2024
AntoineLeleu-Salesforce pushed a commit to AntoineLeleu-Salesforce/Salesforce-Inspector-reloaded that referenced this issue Aug 29, 2024
## Describe your changes

## Issue ticket number and link
Closes tprouvot#500 

## Checklist before requesting a review
- [x] I have read and understand the [Contributions
section](https://github.com/tprouvot/Salesforce-Inspector-reloaded#contributions)
- [x] Target branch is releaseCandidate and not master
- [x] I have performed a self-review of my code
- [x] I ran the [unit
tests](https://github.com/tprouvot/Salesforce-Inspector-reloaded#unit-tests)
and my PR does not break any tests
- [x] I documented the changes I've made on the
[CHANGES.md](https://github.com/tprouvot/Salesforce-Inspector-reloaded/blob/master/CHANGES.md)
and followed actual conventions
- [ ] I added a new section on
[how-to.md](https://github.com/tprouvot/Salesforce-Inspector-reloaded/blob/master/docs/how-to.md)
(optional)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant