-
Notifications
You must be signed in to change notification settings - Fork 11
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
Add support for getting the requested URL from a codelist for documentation #256
Closed
2 tasks
Labels
kind/user-story
Used for issues that describes functionality for our users.
org/ssb
Issues relevant for Statistisk sentralbyrå.
Comments
This was referenced Jun 15, 2023
5 tasks
Nuget v7.14.0-preview.1 created with backend changes. |
5 tasks
This was referenced Nov 9, 2023
Tested for v3 and v4, both work nicely! Well done @Magnusrm ! 🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/user-story
Used for issues that describes functionality for our users.
org/ssb
Issues relevant for Statistisk sentralbyrå.
Description
In order to document the source of a used codelist we need to expose the requested url to the application so we can store and document what the url was when it was used.
Additional Information
Clarifying the usage - it's not required with the url it self, but the parameters used when getting the codelist. The url might often not be generated due to caching. But the parameters will always be passed and can be returned for documentation purposes.
Solution
When backend responds with the options, the metadata/parameters used against the underlying api should be included in the response as a urlencoded header -> X-Altinn-DownstreamParameters
Frontend writes these metadata from the header to a configured field. Add the posibility to configure the datamodel binding to where in the datamodel the values should be stored.
Should be reimplemented with Tanstack Query ref. Altinn/app-frontend-react#1294
Acceptance Criterias
The text was updated successfully, but these errors were encountered: