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.

Sign up for GitHub

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

Jump to bottom

[Setup] Configure editor tools #4

Closed
6 tasks done
zstix opened this issue Aug 13, 2020 · 0 comments · Fixed by #24
Closed
6 tasks done

[Setup] Configure editor tools #4

zstix opened this issue Aug 13, 2020 · 0 comments · Fixed by #24
Assignees
@jerelmiller
Labels
enhancement New feature or request
Projects
Developer Experience Developer Enablement Team
Milestone
MMF 1 - Set Up & ...

Comments

@zstix
Copy link
Contributor

zstix commented Aug 13, 2020 •
edited by jerelmiller
Loading

Summary

To ensure code consistency, we should implement some tools like eslint and prettier. These will be enforced by some CI / git hooks (tracked in a different ticket). See "Helpful Links" section for configuration used on the developer site.

Note that no editor-specific configuration should be added.

Acceptance Criteria

  • babel set up and configured
  • eslint set up and configured
  • prettier set up and configured
  • nvm set up and configured
  • editorconfig set up and configured
  • Jest set up and configured

Helpful Links
@zstix zstix added the enhancement New feature or request label Aug 13, 2020
@zstix zstix added this to the MMF 1 - Set Up & Research milestone Aug 13, 2020
@zstix zstix added the sp:3 label Aug 18, 2020
@zstix zstix added this to To do in Developer Experience Aug 18, 2020
@jerelmiller jerelmiller moved this from To do to In progress in Developer Experience Aug 18, 2020
@jerelmiller jerelmiller self-assigned this Aug 18, 2020
@jerelmiller jerelmiller mentioned this issue Aug 18, 2020
Merged
@zstix zstix moved this from In progress to In Review in Developer Experience Aug 18, 2020
@zstix zstix closed this as completed in #24 Aug 18, 2020
@jerelmiller jerelmiller moved this from In Review to Done in Developer Experience Aug 18, 2020
@rhetoric101 rhetoric101 mentioned this issue Oct 30, 2020
Closed
@kaileyhaynes kaileyhaynes mentioned this issue Jun 14, 2021
Merged
@lchapman4 lchapman4 mentioned this issue Aug 20, 2021
Merged
rhetoric101 pushed a commit that referenced this issue Aug 20, 2021
@lchapman4
TCP API Update
da52d89 
Updated the directions in the doc to remove step #4 since it was unnecessary and didn't match our blog on the same topic.
mfulb pushed a commit to mfulb/docs-website that referenced this issue Sep 21, 2022
Add files needed for LASP tests (newrelic#4)
53e8063
@dneth dneth mentioned this issue Dec 14, 2022
Merged
@zuluecho9 zuluecho9 mentioned this issue Apr 17, 2023
Merged
rhetoric101 pushed a commit that referenced this issue Jan 10, 2024
@moonlight-komorebi
Merge pull request #4 from newrelic/sync_branches_workflow
9d02d9f 
chore: add workflow to sync develop with public develop
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jerelmiller jerelmiller

Labels
enhancement New feature or request
Projects
Developer Enablement Team
Done
Developer Experience
  
Done
Milestone
MMF 1 - Set Up & Research
Development

Successfully merging a pull request may close this issue.

Tooling setup newrelic/docs-website
2 participants
@jerelmiller @zstix