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

feat: Introduce forbidden() #63302

Closed

Commits on Mar 13, 2024

  1. feat: Introduce forbidden()

    ### What?
    Similar to the notFound() function and the `notFound.js` file, this PR follows the convention and introduces the `forbidden()` function along side the `forbiddden.js` file.
    
    ### Why?
    While the available `notFound` and `redirect` functions can get you a long way, there is only so much you can do with them.
    
    Developers need a way to handle the authorized state of a user across the multiple "contexts" next has, by that I am referring to components, api routes, and server actions.
    panteliselef committed Mar 13, 2024
    Configuration menu
    Copy the full SHA
    36c06ee View commit details
    Browse the repository at this point in the history
  2. chore: cleanup

    panteliselef committed Mar 13, 2024
    Configuration menu
    Copy the full SHA
    0de6fad View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    03e8e0f View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    4e9d098 View commit details
    Browse the repository at this point in the history
  5. Configuration menu
    Copy the full SHA
    3f7e3b4 View commit details
    Browse the repository at this point in the history

Commits on Mar 14, 2024

  1. Configuration menu
    Copy the full SHA
    0227cbc View commit details
    Browse the repository at this point in the history