[examples/hackernews] Example OAuth flow.#777
Draft
beauby wants to merge 4208 commits intoSkipLabs:mainfrom
Draft
[examples/hackernews] Example OAuth flow.#777beauby wants to merge 4208 commits intoSkipLabs:mainfrom
beauby wants to merge 4208 commits intoSkipLabs:mainfrom
Conversation
…pLabs#710) Related to previous issues with sequencing of unsubscribe/shutdown, this stops printing spurious error messages surfaced by SkipLabs#708 .
Users might need to know about them, and they are referenced from the docs.
...while we're at it
To ensure all are changed when clang is changed
- Avoid duplicate code - Preparation for updating LLVM
Adds a minimal static analyzer (`shellcheck`) to check our shell scripts. It takes about 3 seconds so I added it to the job that checks formatting
For example `skargo build --skcopt --no-inline --skcopt --no-peephole` will make calls to `skc` start with `--no-inline --no-peephole`. Inspired by `ocamlc`'s `-ccopt`
See [discord thread](https://discord.com/channels/1093901946441703434/1345016769634500698) for context -- triggers were failing to fire on certain updates with null fields, since a row "IS NOT NULL" in postgres only when ALL of its fields are non-null.
Another version bump, this time to pull in SkipLabs#779
- Remove stale `RETURNING id` clauses, following move to the postgres adapter. - Use parameterized queries to avoid sql injections.
Add a dummy login flow (checks only the email, not the password), which allows proper tracking of upvotes and new posts authors. It will also serve as a foundation for the OAuth login example.
Vanity layout feature: add relative time point to each post (eg. "X minutes ago").
Add a special API end point that simulate series of 1 to 20 upvotes to a random post every second.
<img width="898" alt="Screenshot 2025-02-26 at 17 04 50" src="https://github.com/user-attachments/assets/556b54c6-0493-4867-8744-f74de2ebbb74" />
The OAuth client id (resp. secret) is loaded from `examples/hackernews/gh_oauth_client_id.txt` (resp. `examples/hackernews/gh_oauth_secret.txt`).
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
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.
No description provided.