-
Notifications
You must be signed in to change notification settings - Fork 0
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
ADFCONNECT-19100: Neo-Angular-Ramp-up-and-Adjustments (PR Comments) #13
ADFCONNECT-19100: Neo-Angular-Ramp-up-and-Adjustments (PR Comments) #13
Conversation
- removed commented code from styles.scss - removed comments from karma.conf.js - removed code coverage param from test commands - added a new test command that also performs code coverage - upgraded neo to 3.80.6
WalkthroughThe recent updates refine configurations, streamline testing procedures, and optimize style imports. These changes enhance the project's maintainability and testing capabilities, making the development process smoother and more efficient. Changes
Poem
Recent Review DetailsConfiguration used: CodeRabbit UI Files ignored due to path filters (1)
Files selected for processing (3)
Files skipped from review as they are similar to previous changes (2)
Additional comments not posted (1)
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
✅ Deploy Preview for neo-angular-library-storybook ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
- changed some line endings to LF - set eol to LF for new files
} | ||
{ | ||
"git.ignoreLimitWarning": true, | ||
"files.eol": "\n" |
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 probably want your EOL rule in your .editorconfig
(see neo-react's as an example). Putting it here will only affect VSCode, and you should not assume that everyone will always use VSCode.
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.
One suggestion to move your EOL rule, but everything else looks good and makes sense 👍
Closing as I'm about to archive this project. You can re-open when work on this project is started back up. |
Link to updated components in Deploy Preview
Before tagging the team for a review, I have done the following:
Put the most important information here. The content that any reviewer should see and read first (after the PR title).
EXAMPLE IMAGE(S):
[PUT EXAMPLES HERE, such as an image of the new tests, or important use case added by this update]
EXAMPLE FUNCTIONALITY GIF:
[PUT EXAMPLE GIF HERE]
IMPORTANT NOTES:
Summary by CodeRabbit
karma.conf.js
related to Jasmine options.files.eol
in the.vscode/settings.json
file.