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.

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

fix readme #622

Open
Tracked by #666
ljosberinn opened this issue Jun 8, 2022 · 1 comment
Open
Tracked by #666

fix readme #622

ljosberinn opened this issue Jun 8, 2022 · 1 comment
Assignees

Comments

@ljosberinn
Copy link
Owner

  • incremental adoption under features has no explanation other than the code example
  • standalone generation under features still refers to a --generated file which doesnt exist anymore
  • consolidate examples. there are some in collapsibles and some at the bottom, wtf
@ljosberinn ljosberinn self-assigned this Jun 8, 2022
@axelboc
Copy link
Contributor

axelboc commented Aug 9, 2022

I feel like it would be worth having a more typical usage example near the top of the README. Perhaps something that disables/modifies a couple of core ESLint rules and a couple of React rules inside a custom override:

const dependencies = getDependencies();

const customReactOverride = createReactOverride({
  ...dependencies,
  rules: {
    /* some rule overrides */
  }
});

module.exports = createConfig({
  rules: {
    /* some rule overrides */
  },
  overrides: [customReactOverride],
});

@ljosberinn ljosberinn mentioned this issue Aug 11, 2022
9 tasks
@ljosberinn ljosberinn mentioned this issue May 10, 2024
12 tasks
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

No branches or pull requests

2 participants