-
Notifications
You must be signed in to change notification settings - Fork 11
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
Updates to Install and Rules pages #47
Updates to Install and Rules pages #47
Conversation
…cord from 5/22/20
Ino said I was on an older base so the conflicts should be good in this PR instead |
Oh wait, maybe I just am not running prettier on this before committing? @_@; |
also ran npm update for vulnerabilities upgrade typescript and node
Yesss, I did it!!! xD |
Hmm, looks like some formatting has been applied to all files and not just JS/TS ones, which is what the Did you just run |
Hmm.. I believe I ran update, upgrade and run-script format as well in this PR, I can rebase and re-pr without running those. |
Running Doing those things shouldn't have formatted all the rest of the files though. Gonna try to figure it out with you via discord. |
Looks good now regarding the files changed (could do without the package updates, but that's fine for now). I'll let @slassen review the text/content changes. |
I took the liberty of restoring the package files, so they won't cause a lot of conflicts with the other PRs. |
I like the last updated timestamp on terms and conditions. Maybe we can copy this for each section? I would rather have some sort of table for the allowed/disallowed plugins instead of the way it's set up in this PR. I would rather have something in italics instead of another numbered bullet point with a Please use the previous elements and styling on Discord rules. For the "Punishments" section please use a semantic table. |
fixes #5 |
client/src/components/install.jsx
Outdated
@@ -8,7 +8,7 @@ function install(props) { | |||
const { info } = props; | |||
|
|||
return ( | |||
<Container> | |||
<> |
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.
Probably invalid XML. Maybe just comment out? Can clients override style "display: none"?
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.
Man.. I had addon interference in my VSC... really messed me up for a minute there lol but then I discovered how to use Prettier, this next PR should fix any formatting issues.
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.
Can clients override style "display: none"?
I don't think so, when node.js compiles everything it removes all comment lines in the final client .js build files to make it very efficient for production.
…e can copy this for each section? [x * This might take some work, tidied a little for now]I would rather have some sort of table for the allowed/disallowed plugins instead of the way it's set up in this PR. [x]I would rather have something in italics instead of another numbered bullet point with a ^ signaling that it relates to the above point. [x]Please use the previous elements and styling on Discord rules. [x]For the "Punishments" section please use a semantic table.
…-Rules-info-updates
Did this change all the double quotes to single quotes? |
Maybe my prettier config isn't setup right? |
Looking into it. |
Looks like the other way around. Tough to review with so many changes. |
Thank you. Will need to merge with develop to resolve conflicts. |
I was able to choose to force either double quote or single quotes with prettier but I couldn't get it to run without interfering.. |
…-&-Rules-info-updates
I realllly hope I did this right >< I possibly should have changed my merge order slightly but I resolved the conflicts manually which looked like the login-fix pr branch didn't get applied to this branch after some of my reverts and merges, but we should be ready to roll now. Thanks everyone for the patience while I get up and running with git :P |
No problem. I’m sure you’re almost there! I think it would probably be best if you copied just the files of your changes you wanted to make to your desktop then switch to the develop branch and make a new branch/PR. Additionally, please make sure to review and address the points in my previous comment. |
I am so into that idea. This one has gotten a bit messy ^^; |
Compiled from edenxi.com and discord from 5/22/20.
Some formatting changes and info directly added to Install & Rules and some added to config for now