• #16
• #53

In early design, we would like admin to verification every problem/contest created by user.

However, in our later discussion, we decide to remove(decide to not implement them) verification mechanism.

For reference, codeforces don't require admin to verify user submitted content.

Switch normal resource to leptos-query for caching

• https://crates.io/crates/leptos_query

Add new feature: Provide a chat area for each problem.

To do list:

backend

• update migration
• add new database entity
• compare manual database entity with codegen by migration
• add new controller(if we want to cache)

proto

• change database proto

OpenTelemetry Semantic Conventions

Problem

We haven't yet provide any kind of sort for list_by_* rpc, providing such guarantee is useful in many situation.

For example, you have 100 problem in a contest(so you want to use paginator), by guarantee secquence of all problem are sorted in ascending, we can partially render problem without actually retrieve 100 problem from the server.

TODO

• add new paginator-session type (use related_filter() and PaginateCol)
• update comment in backend.proto
• update migration and entity declaration
• implement in backend

• Fix unimplemented rpc
• Update database entity and configure migration
• rewrite/def link permission to allow user link own entity

In current API, we expose a order field for api consumer to set value, them frontend can ask server to order response of list request by that value.

Basic example could be...

1. We have a contest with 0 problem(user want 4 of them)
2. Add Problem A to contest: set problem A's order to 1.0
3. Add problem D to contest: set problem D's order to 2.0
4. Add problem B to contest by inserting in the middle: set problem-B's order to 1.5
5. Add problem C to contest by inserting in the middle: Set problem-C's order to 1.75

In that way, client could list problem in order.

This proposal is intended to move such logic to backend.

the proposed API is similar to such:

message AddToContestRequest{
  required int32 contest_id = 1;
  required int32 problem_id = 2;
  optional string request_id = 3;
}

service Problem{
  /** Add to end of the contest */
  rpc AddToContest(AddToContestRequest) returns (Empty);
}

message InsertRequest{
  optional string request_id = 1;
  optional int32 pivot_id = 2;
  required int32 problem_id = 3;
}

service Contest{
  /** 
   * move the problem to just one after pivot
   * 
   * if pivot is null, insert at front
   */
  rpc insert(InsertRequest) returns (Empty);
}

As the title.

When using leptos-build, run with --pre-compress will compress all static wasm/js/css...

For example:

tree /site/
/site/
├── favicon.ico
├── favicon.ico.br
├── favicon.ico.gz
└── pkg
    ├── mdoj.css
    ├── mdoj.css.br
    ├── mdoj.css.gz
    ├── mdoj.js
    ├── mdoj.js.br
    ├── mdoj.js.gz
    ├── mdoj.wasm
    ├── mdoj.wasm.br
    └── mdoj.wasm.gz

By just serving compressed content, we can save about 70% of bandwidth.

However, leptos-build won't help you serving them, you need to write them in actual code.

A lot config file use default value, so it can be remove

Because I want SSR support, 100% rust / weird js runtime is require

Resource

• syntect
• get cursor
• Codejar

Related

• https://crates.io/crates/trait-variant
• https://github.com/dtolnay/async-trait
• https://github.com/hyperium/tonic/blob/3379d9a6f9efd95b2569aaf34ffbdde6f808113c/tonic-build/src/server.rs#L223

Maybe we need to open a issue to solve this

• change pagination to use optional instead of oneof. (ref)
• split SortBy, example: ProblemSortBy, ContestSortBy.
• decouple SortBy from proto
• rename link to addToContest
• replace bit flag with enum

It seems like clippy doesn't like codegen....

Before working on PartialModel, we should rewrite Pager first.

• decouple pagination logic from Select<E> recreation
• Rewite paginator struct and serialize method to reduce overhead(also eliminate the need of signing session)
• Writer an adopter for Pager

The actual work:

• write PartialModel
• write session update logic
• replace existing Pager

Docker build fail because current Dockerfile only copy member folder.

TODO List

• Fix judger
• Fix backend
• Move more member dependency to workspace dependency

TODO

• Navbar
• Footer
• Login page
• web-grpc api config
• fix ssr error
• Use cookie for token to complete fix ssr error
• Error handling
• #35
• #36
• Contests page
• Rank page
• Submission page
• #39
• #37
• Problem Page
• #38
• #46
• #47
• #57
• Create Contest Page

• Add Solution page
• Add Discussion page
• Add Submission page
• #58
• #48