Repository navigation
Aug 26, 2024
·
1 comments
·
3 replies
Comment options
{{title}}
|
I feel if it's more than just client stuff, api-dispatch might be better suited? |
You must be logged in to vote
All reactions
3 replies
Comment options
{{title}}
|
Yeah, not sure, I also feel that strictly speaking probably api-dispatch is more suitable, but thinking about users, I think probably no user will ever look into that repo, this will be the entry-point for users, and it might be good for users to know how dispatch works. Sort of the same with the microgrid documentation, we have most of it in the SDK, not in api-microgrid. But still I'm not a 100% sure, just more inclined to put it here than in api-dispatch. |
All reactions
Comment options
{{title}}
|
Maybe we can have a less detailed overview for the user side in the client repos? |
All reactions
Comment options
{{title}}
|
What would you remove? |
All reactions
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Select a reply
Loading
reacted with thumbs up emoji
reacted with thumbs down emoji
reacted with laugh emoji
reacted with hooray emoji
reacted with confused emoji
reacted with heart emoji
reacted with rocket emoji
reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
{{title}}
Uh oh!
There was an error while loading. Please reload this page.
We have this in the SDK from the times we thought the dispatch interface will go to the SDK:
But I'm not a 100% sure if to this repo or to https://github.com/frequenz-floss/frequenz-api-dispatch/, and in any case where exactly to put it in the repo. Maybe we can have a new section in the docs with technical docs, or architecture.
FYI @frequenz-floss/api-dispatch-team