generated from wrappid/wrappid-module
-
Notifications
You must be signed in to change notification settings - Fork 3
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
merge: Development into main #22
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
add script to generate header of attribution Ref: #31
fix registry Ref: #28
export to defult exports all files Ref: #28
add script to generate header of attribution Ref: #31
typo in moduleStyles files should be style instead of styles ref #39
add wrappidcare token Ref: #30
Merge branch 'development' of https://github.com/wrappid/wrappid-module into WRPD-enhancement-28 Ref #28
update changes package-lock.json Ref: #28
enhancement: revamp to typescript related issue fix
fix service compilation error Ref: #42
fix(core): :bugfix: ts compilation error
code lint fix and update eslintrc file Ref: #45
refactor: 🎨 fix eslint
merge: from Development
import/resolver configuration in your ESLint configuration file Ref: #48
remove unnecessary quotes in keys in elsintrc config file Ref: #48
fix: configure ESLint to recognize the module path
merge: from Development
update code style script to only check for added and modified files only, and apply lint check Ref: #19
bugfix(config): 🔧 update code style script pr-guardrails
merge: development into main
update code style script to only check for added and modified files only, and apply lint check Ref: #19
change npm installation approach to npm ci Ref: #53
change caret to tilde package.json, generate package-lock.json Ref: #54
enhancement: pr guardrails and package.json dependencies.
update package json and set jest testing configuration Ref: #56
chore(global): ✨ jest config set
fix naming convention of registry files Ref: #58
tag creation on pull request merges Ref: #60
style(global): ♻️ fix naming convention of registry files
feat(config): ✨ tag release of wrappid module template
add standard version package and script to release tag Ref: #60
feature: template release
create new tag ref: NA
add top header content Ref: #63
feat(utils): 📝 update attribution generation script
create new tag ref: NA
All the registry name should be from camelCase to PascalCase in the service/registry files Ref #65
refactor(core): ♻️ registry names camelCase to PascalCase
create new tag ref: NA
Merge remote-tracking branch 'template/main' into WRPD-refactor-13 Ref: #13
enhancement: update template
anantakumarghosh
approved these changes
Mar 20, 2024
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.
👍
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.
Description
Clearly describe the changes you've made in this pull request. Explain the purpose and reasoning behind the changes. Reference any relevant issues or discussions using keywords like "Fixes #<issue_number>" or "Resolves #<issue_number>".
Related Issues
Testing
Checklist
Screenshots (if applicable)
Additional Notes
Reviewers
Maintainer Notes