Stephen Wicklund issues

Results 189 issues of


                                            Stephen Wicklund

MS each subscription endpoint also has a "query" alternative, that just returns the current contents (should share same pipeline as subscription endpoints)

backend

Clean up frontend code to use permission-check logic that matches the logic of the rust backend (ie. based on access-policies consistently, rather than just is-user-creator-or-mod checks)

MS if there are more than three premises in an argument, the 4th+ premises start out hidden behind a limit-bar

frontend

Add a special-expand button to right of node-toolbar, which expands to show: special child-groups (eg. one relating to curation and such)

Expand readme to include instructions on building+running the app-server locally, without need for docker at all (important for easier dev-onboarding; docker only needed for dev of monitor-backend and such, and for deploying to cloud)

Make-so the js bundles are faster to build, by switching from webpack+babel to rspack (or other fast alternative)

Some possible bundlers: * rspack + swc * swc (ie. its own bundler) * esbuild The current plan is to try to use RSPack, since it seems to be the...

frontend

Probably set up the app-server cargo-build in docker to automatically record the "build timings" html file into a git-version-controlled location (or at least local accumulator folder) for easy historical analysis [and/or a git-tracked file with custom format that records the dependency tree along with the compile time, bonus if it examines the git-history to guess how compile-time deltas from dependency-changes]

Fix that db dumps cannot currently be restored as-is

Issue 1) Due to dependency ordering Specifically: The problem stems from the cached-tsvector columns referencing utility functions, which pg-dump is placing after the table-creation lines in the sql dump. Another...

Fix error in TermPlaceholder.tsx, when viewing an "equation" node that has term-referencing inside it

frontend

Fix that usage of node-layout algorithm currently is not preserving the "fair split" between pro and con children (ie. the split should be directly to the right of the parent node)

frontend