Skip to content
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

Dashboard skeleton #4

Open
wants to merge 49 commits into
base: master
Choose a base branch
from
Open

Conversation

kaffein
Copy link
Member

@kaffein kaffein commented Apr 25, 2020

This PR implements the overall structure and skeleton of the UI.

This is still a WIP but I would like to have it here as a draft PR so that you guys can follow up. Again do not hesitate to make suggestions on how we can improve it.

@kaffein kaffein requested a review from devth April 25, 2020 15:24
@kaffein kaffein self-assigned this Apr 25, 2020
@devth
Copy link
Member

devth commented Apr 25, 2020

Cool, looks good so far!

@kaffein kaffein marked this pull request as ready for review June 10, 2020 16:10
@kaffein
Copy link
Member Author

kaffein commented Jun 10, 2020

Can you PTAL @devth :) especially the CSS part haha

thanks in advance

Since we are using leiningen to manage dependencies, we have to make sure to
include/align the versions of the dependencies with those pulled by shadow-cljs,
especially those involving closure-compiler.
Instead, if we opt to use shadow-cljs at some point, all the issues related to
dependencies is solved by the tool and we would not have to deal with those as
explained here by Thomas Heller : https://clojurians-log.clojureverse.org/shadow-cljs/2020-01-06
Since our main build tool is leiningen, we added a few aliases to allow
it to interact with shadow-cljs.
 * lein watch : starts a new shadow-cljs watch process
 * lein compile : simply compiles the project
 * lein release : compiles the project for a production (minified js for each module)
 * lein cljs-repl : starts a clojurescript repl within the context of the app
Some new instructions were added regarding the use of leiningen as an
entrypoint for managing shadow-cljs and the whole front-end building
process
Since lein-shadow plugin now generates shadow-cljs.edn from the configuration
entry in project.clj, this file is not needed anymore
To ease development, leiningen has been removed. Shadow-cljs provides
a very efficient and lightweight way during development.
Leiningen will eventually be added (if needed) at the end to comply
with the other Yetibot projects which already use it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants