Skip to content
This repository has been archived by the owner on Dec 12, 2023. It is now read-only.

Protected / Serverside only property? #67

Open
BananaAcid opened this issue Feb 14, 2023 · 0 comments
Open

Protected / Serverside only property? #67

BananaAcid opened this issue Feb 14, 2023 · 0 comments
Labels
question Further information is requested

Comments

@BananaAcid
Copy link

BananaAcid commented Feb 14, 2023

Ask your question

Is there a way to have some of the data only available on the server side, without completely disabling the routes?

Additional information

Protected: disabling keys that can not be POSTed to route (like id is already, if i saw that correctly)

Server side only: keys that will not be send (filtered out before GET)

Main reasons:

  • Carrying login status and fetched userdata should only stay on the server side,
  • other data like user id and name should be retrievable by using the routes.
@BananaAcid BananaAcid added the question Further information is requested label Feb 14, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant