twentyhq/twenty
1
1
Fork 0
mirror of https://github.com/twentyhq/twenty.git synced 2024-12-18 09:02:11 +03:00
Code Issues Packages Projects Releases Wiki Activity
b6e1853d9f
twenty/.vscode/extensions.json

17 lines
454 B
JSON
Raw Normal View History

I can open the project in GitHub (#92) * Ignore node_modules * Use bash-compatible dotenv format While still being compatible with dotenv, this also allows sourcing the file to export all variables in bash. * Add prettier extension to recommendations * Move to port 5001 to avoid conflict with macOS services * Add workspace * Add devcontainer This automatically starts with all environment variables available locally. It brings up services which are dependent on each other individually and verifies health before moving on to the next service. * Split init into clean, up, and logs tasks. This allows the developer to set up .env and .npmrc files before running services, and does not require starting from a clean db every time the devcontainer is restarted. * Copy .env when creating codespace * Automatically run UP command upon devcontainer creation * Fix log message --------- Co-authored-by: Felix Malfait <felix.malfait@gmail.com>
2023-05-03 12:34:10 +03:00
{
"recommendations": [
"ms-vscode-remote.remote-containers",
Add VSCode extensions (#283)
2023-06-14 18:20:12 +03:00
"styled-components.vscode-styled-components",
Lucas/t 364 on comment drawer i can fetch all comment threads with (#193) * Added prisma to suggested extension in container * Added comments and authors on drawer with proper resolving * Fix lint * Fix console log * Fixed generated front graphql from rebase
2023-06-05 16:23:29 +03:00
"dbaeumer.vscode-eslint",
Add VSCode extensions (#283)
2023-06-14 18:20:12 +03:00
"unifiedjs.vscode-mdx",
"ms-vscode.makefile-tools",
"ms-azuretools.vscode-docker",
"esbenp.prettier-vscode",
"GraphQL.vscode-graphql",
"prisma.prisma",
"unifiedjs.vscode-mdx",
"yoavbls.pretty-ts-errors",
"graphql.vscode-graphql-syntax",
"graphql.vscode-graphql"
I can open the project in GitHub (#92) * Ignore node_modules * Use bash-compatible dotenv format While still being compatible with dotenv, this also allows sourcing the file to export all variables in bash. * Add prettier extension to recommendations * Move to port 5001 to avoid conflict with macOS services * Add workspace * Add devcontainer This automatically starts with all environment variables available locally. It brings up services which are dependent on each other individually and verifies health before moving on to the next service. * Split init into clean, up, and logs tasks. This allows the developer to set up .env and .npmrc files before running services, and does not require starting from a clean db every time the devcontainer is restarted. * Copy .env when creating codespace * Automatically run UP command upon devcontainer creation * Fix log message --------- Co-authored-by: Felix Malfait <felix.malfait@gmail.com>
2023-05-03 12:34:10 +03:00
]
}
Reference in New Issue Copy Permalink