forked from segmentio/typewriter
-
Notifications
You must be signed in to change notification settings - Fork 2
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
chore: run prettier format for all files #23
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ssbeefeater
approved these changes
May 15, 2024
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #23 +/- ##
========================================
Coverage 88.82% 88.82%
========================================
Files 3 3
Lines 170 170
Branches 58 58
========================================
Hits 151 151
Misses 17 17
Partials 2 2 ☔ View full report in Codecov by Sentry. |
akashrpo
added a commit
that referenced
this pull request
Jul 24, 2024
* chore: run prettier format for all files (#23) * chore: add prettier script * chore: run format command * chore: update yarn package * feat: tracking plan v2 api temp change (#19) * feat: package typer init * feat: add build code * feat: update code * feat: update code * feat: add temp tp version change * feat: update name * feat: add new TP api v2 integration * feat: cleanup * feat: remove null properties * feat(tracking-plan): refactor * fix: draft new release for histories (#26) * fix: draft new release for histories 2 (#27) * fix: draft new release for histories 3 (#28) * fix: draft new release for histories 4 (#29) * feat: draft new release 5 (#31) * v1.0.0-beta.7 --------- Co-authored-by: Akash Gupta <[email protected]> Co-authored-by: GitHub actions <[email protected]>
akashrpo
added a commit
that referenced
this pull request
Jul 26, 2024
* chore: run prettier format for all files (#23) * chore: add prettier script * chore: run format command * chore: update yarn package * feat: tracking plan v2 api temp change (#19) * feat: package typer init * feat: add build code * feat: update code * feat: update code * feat: add temp tp version change * feat: update name * feat: add new TP api v2 integration * feat: cleanup * feat: remove null properties * feat(tracking-plan): refactor * fix: draft new release for histories (#26) * fix: draft new release for histories 2 (#27) * fix: draft new release for histories 3 (#28) * fix: draft new release for histories 4 (#29) * feat: draft new release 5 (#31) * v1.0.0-beta.7 --------- Co-authored-by: Akash Gupta <[email protected]> Co-authored-by: GitHub actions <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thanks for taking the time to contribute to RudderTyper!
It is highly appreciated that you take the time to help improve RudderTyper.
We appreciate it if you would take the time to document your Pull Request.
Sadly, if we don't receive enough information, or the Pull Request doesn't
align well with our roadmap, we might respectfully thank you for your time, and close the issue.
Respect earns Respect 👏
Please respect our Code of Conduct, in short: