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

[RFR] Replace tslint with eslint #3321

Merged
merged 22 commits into from
Jun 16, 2019
Merged

[RFR] Replace tslint with eslint #3321

merged 22 commits into from
Jun 16, 2019

Conversation

djhi
Copy link
Contributor

@djhi djhi commented Jun 8, 2019

  • Replace tslint with eslint
  • Adjust configuration
  • Replace all tslint comments with eslint ones

@djhi djhi added this to the 3.0.0 milestone Jun 8, 2019
examples/simple/src/comments/PostPreview.js Show resolved Hide resolved
packages/ra-core/src/controller/EditController.tsx Outdated Show resolved Hide resolved
@@ -73,9 +73,6 @@ interface Props {
const ShowController = (props: Props) => {
useCheckMinimumRequiredProps('Show', ['basePath', 'resource'], props);
const { basePath, children, id, resource } = props;
if (!children) {
Copy link
Member

Choose a reason for hiding this comment

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

same

@djhi djhi changed the title [RFR] Replace tslint with eslint [WIP] Replace tslint with eslint Jun 8, 2019
Copy link
Member

@fzaninotto fzaninotto left a comment

Choose a reason for hiding this comment

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

You'll need a small rebase

@djhi djhi force-pushed the replace-tslint-with-eslint branch from 2d7cd13 to fe2e31e Compare June 12, 2019 07:27
@djhi djhi changed the title [WIP] Replace tslint with eslint [RFR] Replace tslint with eslint Jun 13, 2019
Copy link
Member

@fzaninotto fzaninotto left a comment

Choose a reason for hiding this comment

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

final touches...

case DELETE:
return {
id: params.id,
};
default:
console.log('Unknown fetch verb');
Copy link
Member

Choose a reason for hiding this comment

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

No, unknown fetch verbs are allowed and can be implemented in custom dataProviders

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Those dataProviders did not handle them at all and returned undefined. How should we handle that ?

case DELETE:
return {
id: preparedParams.id,
};
default:
console.log('Unknown fetch verb');
Copy link
Member

Choose a reason for hiding this comment

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

Same, we don't mind unknown fetch verbs

@djhi djhi force-pushed the replace-tslint-with-eslint branch from 708f445 to bbaf62a Compare June 15, 2019 09:04
@fzaninotto fzaninotto merged commit 7eced13 into next Jun 16, 2019
@fzaninotto fzaninotto deleted the replace-tslint-with-eslint branch June 16, 2019 18:52
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.

None yet

2 participants