Skip to content

chore: Keep Nuxt's 'asyncData' and 'fetch' with 'data' #823

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 4 commits into from
Aug 17, 2019
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 1 addition & 3 deletions lib/rules/order-in-components.js
Original file line number Diff line number Diff line change
Expand Up @@ -19,11 +19,9 @@ const defaultOrder = [
'inheritAttrs',
'model',
['props', 'propsData'],
'data',
['asyncData', 'fetch', 'data'],
Copy link

Choose a reason for hiding this comment

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

I suggest moving fetch to the top of asyncData because it is more context less

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@pi0 but as I understand, having asyncData and fetch in same array means the order can be freely chosen between those. Then it shouldn't be need for moving them around?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

OK, I have actually updated to have them in explicit order.

'computed',
'watch',
'asyncData',
'fetch',
'LIFECYCLE_HOOKS',
'methods',
['template', 'render'],
Expand Down