-
Notifications
You must be signed in to change notification settings - Fork 16
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
Changed Source-parameter in editFormUrl #530
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Strålende
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good @siifux 🔪
@siifux This is not working. It continues to catch to report you are "coming from" before you created a new report. Please add a "How to test" section fr the next test :-) |
Most likely the shared-package from npm is used, which is not current. Let's put effort into publishing the shared-package before investing any more time into this. |
Working on creating a puzzlepart-user on npm that has access to the packages. |
Sent an email to npm support. I had For now (as a temp fix) I can give the other people on the PP team access with their npm users. Just give me your usernames on npmjs.com and I'll fix it @siifux @tarjeieo @Remi749 @Rundez @TinHoangVu |
Tested this, and works as expected with the npm packages updated 👏 |
Working well in both upgraded and fresh install |
Description
I have changed the Url that is set as a
&Source
parameter to not include the query param, so that you won't be redirected back to the spesific status report you came from. I have read the examples written in the docs for Location, and I think this solution will grab the Url without the query/hash.