Closed acelaya closed 1 year ago
Hi @acelaya, it's great! would then be possible to export the chart data?
Hey @garethjax.
That's something I have considered many times. Could you please open a separate feature request ticket for that?
of course!
All preparations are done.
Hey, we're interested by this project! Is there any ETA for the Shlink Dashboard? Any way to help? Any todo list?
Shlink web client is a fully static web app, with no backend.
That's pretty convenient, and simplifies a lot of things, but also introduces some limitations.
Since there has been requests for this in the past, I'm considering a new shlink-dashboard project, which would be a web client but with its own backend for frontend.
In order to do it, we need to split shlink-web-client, having a subcomponent which wraps all the operations done when you are connected to a server.
This component would be reused by both shlink-web-client and shlink-dashboard, and the list of servers, configs, etc, would be handled differently by each one of them.
It should aslo allow (at some point) to provide the list of permissions, so that shlink-dashboard can "hide" sections based on the user's permissions.
Once the component has been split (shlink-web-component?), it can be moved to its own repo and published separately as an npm package.
TODO
Result
Message
SimpleCard
SearchField
DropdownBtn
RowDropdownBtn
InputFormGroup
Checkbox
,ToggleSwitch
andBooleanControl
NavPills
andNavPillItem
OrderingDropdown
and order helpers.useDomId
useElementRef
useToggle
base.scss
which is distributed uncompiled and then imported wherever needed.Extracted component
Potential component names:
<Shlink />
<ShlinkWebComponent />
<ShlinkWeb />
<ShlinkClient />
<ShlinkApp />
Usage:
Peer dependencies: