-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Workshop app - Phase 1 #831
base: main
Are you sure you want to change the base?
Conversation
@brandonfancher & @Velua can you please review the UI structure, the form hooks etc. To make sure it is aligned with the other frontend apps patterns? @James-Mart package wip, need to sync with you! |
8eafc2e
to
0d234b5
Compare
0d234b5
to
1080ead
Compare
} | ||
|
||
#[action] | ||
fn storeSys(path: String, contentType: String, content: Hex<Vec<u8>>) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
storeSys
(and therefore the WebContentTable
) should be in the query service alongside serveSys
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
when I read query my first instinct was that it is a read only service (I thought the same when I saw the example named r-<package>
). If we are adding the storesys it would go against a query or a read only service. So what is the definition of the query service on the package?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A query service's primary job is to handle HTTP requests. In this mode it is read-only. The data is stored in the query service because it is only used for the HTTP interface. It's essentially static content associated with the service.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I might prefer calling it an "http-server" or something. Query / RPC service don't seem as readily understandable.
/// Holds metadata for a registered app | ||
#[table(name = "AppMetadataTable", index = 0)] | ||
#[derive(Debug, Clone, Fracpack, ToSchema, Serialize, Deserialize, SimpleObject)] | ||
pub struct AppMetadata { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These weren't in the github issue (until right now because I just added them), but could you also add
tags: List<String>
- Devs can add up to 3 tags that can further be used to categorize the applicationcreated: TimePointSec
- This can be set with gettingcurrentBlock().time
from theTransact
service. Tracks the unix time in seconds that the app was registered.
This looks good. I see that some of the UI and account selection controls were borrowed from webmail/chainmail. There is a newer in-progress (will be merged soon) branch of that that actually queries available accounts and changes the account with supervisor from the dropdown (vs. using the mocked out accounts list fixture.) That can be found in the UI code wise, everything looks great! |
Dark mode, pretty please! |
@swatanabe can you please help me troubleshoot why I'm receiving the error below when running
|
It's triggered by When trying to resolve "r-workshop" we look at the workspace members and the immediate dependencies of "workshop". "r-workshop" isn't in either. |
wip...