Skip to content

NEW (eslint): @W-16113415@: Implement the runRules method of eslint engine #41

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

Merged
merged 2 commits into from
Jul 10, 2024

Conversation

stephen-carter-at-sf
Copy link
Collaborator

@stephen-carter-at-sf stephen-carter-at-sf commented Jul 9, 2024

No description provided.

@stephen-carter-at-sf stephen-carter-at-sf force-pushed the sc/W-16113415 branch 4 times, most recently from c856d2c to 792d7ff Compare July 10, 2024 13:17
Base automatically changed from sc/W-16113413 to dev July 10, 2024 14:00
@stephen-carter-at-sf stephen-carter-at-sf changed the base branch from dev to sc/W-16113413 July 10, 2024 14:08
@stephen-carter-at-sf stephen-carter-at-sf changed the base branch from sc/W-16113413 to dev July 10, 2024 14:15
@stephen-carter-at-sf stephen-carter-at-sf marked this pull request as ready for review July 10, 2024 14:15
Comment on lines +16 to +20
/**
* NOTE THAT WE WANT TO KEEP THE AMOUNT OF TESTS HERE TO A MINIMUM!
* All functionality should be tested at the unit level. This file ideally should only contain 1 (maybe 2) tests
* at most to simply confirm that things can wire up correctly without failure.
*/
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Currently these tests don't provide much value over the actual engine tests... so if you are wondering why I have them, it is part of a bigger picture idea:

I'd like to create a pseudo end to end test for each engine... so that eventually we can see the common overlapping pattern between them all which will eventually help me create a generalized end-to-end test utility that can live in the engine api (which will eventually help engine api authors to testing more easily). After one or two more engines, i think we'll have enough information to then create the generalized utility.

@stephen-carter-at-sf stephen-carter-at-sf merged commit f947638 into dev Jul 10, 2024
5 checks passed
@stephen-carter-at-sf stephen-carter-at-sf deleted the sc/W-16113415 branch July 10, 2024 16:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants