Tilgangskontroll siste 14a vedtak #662
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…tte på controller-nivå og gjer "SKRIVE" til default-argument
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Denne PR-en gjer i hovedsak to ting:
tilgangType-parameter slik at vi skal kunne skilje på kva type tilgangskontroll (SKRIVEellerLESE) vi ønskjer å bruke for dei ulike endepunkta våraSKRIVE- dette var mest for å sleppe å sende inn det nye argumentet overalt kor det skal vere uendra - eg endte likevel opp med å måtte bruke name-arguments ved callsite for at kompilatoren skulle verte glad, så vi kan vurdere å ikkje bruke default-argument fortilgangTypeog heller spesifisere dette overalt/hent-siste-14a-vedtak-endepunktet frå å kreveSKRIVE-tilgang til å no berre kreveLESE-tilgang, då vi meinar det er ein bug/feil at vi har krevSKRIVE-tilgang