-
Notifications
You must be signed in to change notification settings - Fork 174
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
Overhaul the Domain server's onboarding wizard. #1344
Overhaul the Domain server's onboarding wizard. #1344
Conversation
…ail issue present)
The following links are available:
build (macOS-latest, full) build (macOS-latest, client) build (windows-latest, full) |
The following links are available: build (macOS-latest, full) build (ubuntu-18.04, full)
build (windows-latest, full) |
Did you intend to include the files in the /dist (i.e., build?) directory in the PR? |
On setting up an admin account, I made some mistake because I couldn't log into the browser again. Looking at AppData/Roaming/Vircadia - PR1344/domain-server/config.json, I discovered that I had input "Misterblue" and trying to login with "misterblue" failed. Logging in the "Misterblue" worked. |
It was the latest chrome. I believe I'm set on light mode. But the other dialogues worked fine, it was just the admin login dialogue that was the wrong colors |
It seems weird to commit files in the /dist (i.e., build) directory. |
You're right, it's the quick and easy way to do it. The alternative is to have it trigger like the server-console as a CMake step because it would be necessary for it to be built at compile time using npm then Quasar. I think that's something that can and probably should be setup at some point: a resources bootstrap step that we can toss this and any future NPM commands into.
|
Some build instructions should be added on how to build and commit updates. |
Are there any sorts of specific instructions needed? So far there is a README.md explaining how to work with the project. |
In the "Build the app" section perhaps something along the lines of...
|
The following links are available:
build (windows-latest, full) |
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.
Looks OK though I haven't properly reviewed the Vue-related items because I don't know Vue.
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 don't see anything wrong with the Vue code (based on my limited knowledge of same).
Some misc comments and questions were added.
import axios, { AxiosInstance } from "axios"; | ||
import Log from "../modules/utilities/log"; | ||
|
||
declare module "@vue/runtime-core" { |
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.
There should be a comment that is declarization adds ".$axios" reference to all Vue components.
And, is this in addition to the addition of ".$axios" to app.config.globalProperties done below?
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.
Honestly, I couldn't tell you exactly how this works as it's boilerplate since I bootstrapped the project with Quasar CLI to include Axios.
domain-server/resources/web/web-new/src/components/components/login/MetaverseLogin.vue
Show resolved
Hide resolved
domain-server/resources/web/web-new/src/components/dialogs/ConnectMetaverse.vue
Show resolved
Hide resolved
domain-server/resources/web/web-new/src/pages/FirstTimeWizard/Index.vue
Outdated
Show resolved
Hide resolved
domain-server/src/DomainServer.cpp
Outdated
@@ -86,7 +86,16 @@ bool DomainServer::_getTempName { false }; | |||
QString DomainServer::_userConfigFilename; | |||
int DomainServer::_parentPID { -1 }; | |||
|
|||
/// @brief Route a request to the Metaverse server. | |||
/// @param connection The HTTP connection object. | |||
/// @param requestUrl The full URL of the request. |
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.
The comment should mention the optional 'key' query. This doesn't say much about what a "full URL" could possibly be.
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 don't see anything regarding an optional key query in the parameters for this function.
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 might have misunderstood the added code. It looks like code was added to check the query parameters on the requestUrl for the presence of different fields. This is not made clear in the description or explanation of the function.
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've updated it. Also the added code replaces the old code. The old code was not working correctly, so I did it a different way while fixing it.
…mni/vircadia into feature/new-domain-wizard
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.
Worked great.
QA: Please go ahead and download this and give feedback about the general flow of things and if there are any issues.
completed_once
tofalse
to force the tutorial to show up again.