Infrastructure/logto
0
Fork 0
mirror of https://github.com/logto-io/logto.git synced 2025-01-06 20:40:08 -05:00
Code Issues Activity

chore(console): update php and python guide (#4964)

Browse source
This commit is contained in:
Gao Sun 2023-11-29 15:43:49 +08:00 committed by GitHub
parent 15278302f3
commit e49e92fb6f
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 3 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
packages/console/src/assets/docs/guides/web-php/README.mdx
View file

@ -147,7 +147,7 @@ To clean up the Python session and Logto session, we can designate a post sign-o
And a sign-out route can be implemented as follows:
<pre>
<code className="language-python">
<code className="language-php">
{`Route::get('/sign-out', function () {
return redirect(
// Redirect the user to the home page after a successful sign-out

2
packages/console/src/assets/docs/guides/web-python/README.mdx
View file

@ -199,6 +199,8 @@ Now, you can test your application:
Now, you have a working sign-in flow, but your routes are still unprotected. Per the framework you use, you can create a decorator such as `@authenticated` to protect your routes. For example:
```python
from functools import wraps
def authenticated(func):
@wraps(func)
async def wrapper(*args, **kwargs):