Add LESTI 2025/2026 curriculum content - #16
marcelo-m7 wants to merge 1 commit into
Conversation
There was a problem hiding this comment.
Codex Review: Here are some suggestions.
Reply with @codex fix comments to fix any unresolved comments.
About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you open a pull request for review, mark a draft as ready, or comment "@codex review". If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex fix this CI failure" or "@codex address that feedback".
| --- | ||
| slug: "seguranca-web" | ||
| title: "Segurança Web" | ||
| summary: "Mitigação de vulnerabilidades comuns como SQL Injection, XSS e CSRF." | ||
| youtube_playlists: | ||
| - id: "PL-TOPIC-seguranca-web" | ||
| priority: 1 | ||
| tags: | ||
| - "OWASP" | ||
| - "SQL Injection" | ||
| - "XSS" | ||
| type: topic | ||
| layout: topic |
There was a problem hiding this comment.
[P1] Ensure topic slugs are unique across modules
The topic page declares slug: "seguranca-web", but the same slug is also defined in uc/19411049/seguranca-web.md. Because the Supabase schema models subjects.topic with slug as the primary key, inserting both files will clash—either the sync will fail on a duplicate key or one UC’s topic will silently overwrite the other. Consider deduplicating the content or assigning distinct slugs so each topic can be stored and referenced independently.
Useful? React with 👍 / 👎.
Summary
Testing
https://chatgpt.com/codex/tasks/task_e_68cf0180cb1c8322813c766c52b85704