-
Notifications
You must be signed in to change notification settings - Fork 437
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
feat: IDE Integration #1630
feat: IDE Integration #1630
Conversation
Better integrate VS Code and into the project. Update `.gitignore` to encompass more generated content and better Sublime Text generated content. Update Dev Container configs and base images. Integrate VS Code debugging support. Randomize SA password.
These should not be present any more since the config is now a workspace config instead of a folder config.
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.
Thank you for the PR. I just added few question based on my limited knowledge on IDE setup. It will still be better to get some feed back from @arthurschreiber to finalize the changes within the PR.
"files.trimTrailingWhitespace": true, | ||
"files.insertFinalNewline": true, | ||
"files.trimFinalNewlines": true | ||
} |
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 saw these configuration are moved into Tedious.code-workspace. Is settings.json becoming a outdated way to handle this or it is just simpler to do this within the Tedious.code-workspace?
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.
settings.json is fully supported and not going away to the best of my knowledge.
I believe it is simpler as you can centralize more configurations in the workspace config. It technically gives you more capabilities as settings.json relates only to a single set of configurations for the folder, the configuration of the workspace allows for more options and integrations and I believe it also has codespace support.
Some examples are folder exclusions on the workspace to hide stuff that is not necessary, this is not supported on settings.json
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.
You can also include extension recommendations in the same file.
It is also better for monolithic projects.
@@ -21,7 +21,7 @@ services: | |||
|
|||
environment: | |||
- "ACCEPT_EULA=Y" | |||
- "SA_PASSWORD=yourStrong(!)Password" | |||
- "MSSQL_SA_PASSWORD=QhNemHjCWHui9vNnRC.TMRAhusvM3n9_" |
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.
May I ask is this password here generated in someway during the run time?
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.
It is not generated, I just regenerated the password to reduce reliance on hardcoded non-random passwords.
It doesn't change any behavior.
I did update the environmental variable name as the one that was used is no longer supported.
Changes:
settings.json
file).gitignore
from GitHub forSublime Text
andNode.JS
.