Skip to content

Conversation

f
Copy link
Owner

@f f commented Jun 6, 2018

v1.0.0

  • A complete rewrite, more extensible.
  • Readable and better code.
  • Update to Webpack 4
  • Remove built-in loaders. Maybe we can create another repository including custom spinners.
  • Remove width and height props.
  • Strict props.
  • isLoading supports matcher now.
  • Rename registerComponents to registerComponent
  • Added accessorName option to change $vueLoading key.
  • Removed createActionHelpers, use mapLoadingActions or wrapLoading instead.

@f f requested a review from sky-code June 6, 2018 12:42
@f
Copy link
Owner Author

f commented Jun 6, 2018

@sky-code I'm in rewriting progress. Can you please review?

@f
Copy link
Owner Author

f commented Jun 6, 2018

Diff view is untrackable, please pull and view code on your editor :)

@f f changed the title WIP: 1.0.0 1.0.0 Jun 6, 2018

node_js:
- 5
- 10
Copy link
Contributor

Choose a reason for hiding this comment

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

Is it compatible with Node 8?

Copy link
Owner Author

Choose a reason for hiding this comment

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

Possibly yes. Not tested.

README.md Outdated

```html
<template>
<progress-bar v-if="$vueLoading.isLoading(/creating.*/)">Creating something...</progress-bar>
Copy link
Contributor

Choose a reason for hiding this comment

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

Dot requires escaping. WDYT about using wildcards? It simpler and not requires escaping. We can outsource it to library like https://github.com/sindresorhus/matcher

@Koc
Copy link
Contributor

Koc commented Jun 6, 2018

Code is much better readable now. Can you fix #28 also before 1.0, please?

And WDYT about repository rename? To vue-loading (and remove paragraph about misleading about Vuex).

@f
Copy link
Owner Author

f commented Jun 6, 2018

I think #28 is fixed with vuexModuleName option. Now no named property is hardcoded, everything is configurable.

I'm thinking about renaming the project but vue-loading is already registered. Maybe we can find another fancy name.

@Koc
Copy link
Contributor

Koc commented Jun 6, 2018

I think #28 is fixed with vuexModuleName option. Now no named property is hardcoded, everything is configurable.

So should I use different vuexModuleName for each Vue instance? If yes - it doesn't sove issue, because we need share same module between different instances.

throw new Error('[vuex-loading] Vuex not initialized.');
}
this.store = store;
store.registerModule(vuexModuleName, vuexStore);
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe it is possible to check here - if module with same name already registered and if yes - skip registration? Can you add test case for multiple Vue instances on same page?

Copy link
Owner Author

Choose a reason for hiding this comment

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

This makes sense. I'm going to.

Copy link
Owner Author

Choose a reason for hiding this comment

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

Vuex doesn't give me the info about if the module is registered, so I unregister it first.

@Koc Koc mentioned this pull request Jun 6, 2018
@f
Copy link
Owner Author

f commented Jun 6, 2018

Added some useful directives. ec2db9d

@f f merged commit 0869a6e into master Jun 7, 2018
@f f deleted the 1.0.0 branch June 7, 2018 07:57
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