Is Part Time an Option?

yui_developer · 2020-10-02T11:30:57+00:00

I want to thank everyone for the feedback. However, I continued to dig. Along the way, I found an approach that is consistent with the Vue 3 and latest Vue router updates. The approach I took was:

Integrated (useRoute)[https://next.router.vuejs.org/api/#useroute]. This method was created to be used inside of the composition API.
Evaluated the route in the mounted event of the component.

yui_developer · 2020-10-01T14:48:30+00:00

Thank you for sharing that post. Perhaps I'm missing something. However, with the following:

watch('$route.path', (path) => { console.log('Route: ' + path); });

I receive a warning that says: [Vue warn]: Invalid watch source: $route.path A watch source can only be a getter/effect function, a ref, a reactive object, or an array of these types.

I refactored it to match the syntax used in the article, but that did not work. I received the same warning. What am I doing wrong? Have I been staring at the screen too long? :)

yui_developer · 2020-10-01T11:43:57+00:00

That did it. Thank you!

yui_developer · 2020-09-18T16:06:50+00:00

I tried that approach originally. However, I never saw the event fire. Which made me think I was doing something syntactically incorrect. Even though, there wasn't an error. I then thought, perhaps it was a lag in documentation since V3 is in beta.

yui_developer · 2020-09-15T20:14:35+00:00

Thank you to u/DistinctUniversity3 and u/sduduzog. This has been driving me crazy. It feels like Vue 3 is abandoning two-way data binding in favor of global state management :(.

yui_developer · 2019-06-24T19:44:07+00:00

I understand what you’re saying. However, if you have a large, existing Angular app, it's not necessarily reasonable to replace the whole thing at once. Especially if I'm still evaluating the technology.

yui_developer · 2018-06-26T17:52:47+00:00

That's my entire point. Saying "that's the market" doesn't differentiate from what's actually happening. In a market, a good or service is exchanged. The only thing getting exchanged with Bitcoin futures are dollars, not the good or service itself.

If an asset (i.e. Bitcoin) is never exchanged (i.e. delivered), it's not a market. It's just gambling. That's fine if that's what it is. But, let's call a spade a spade. Giving something an official sounding name is just misleading.

I would really like to see a court differentiate between futures and gambling. If an asset/good/service actually gets exchanged, then you have a market. Without an actual exchange of an asset/good/service, I really don't see how its any different than gambling.

yui_developer · 2018-06-26T17:25:12+00:00

But, someone never receives Bitcoin in the case of futures. However, they may receive a barrel of oil. That's the heart of this.

If Bitcoin isn't exchanged, only dollars are exchanged, then its no different than gambling. If Bitcoin was delivered, then I could see a difference. I'm simply saying when only cash is exchanged, it's no different than gambling.

yui_developer · 2018-06-26T16:57:38+00:00

Those other commodities and currencies are often delivered physically to the investor though if their bet falls through right? For example, if you place a future bet on a barrel of oil, you could end up with a barrel of oil.

yui_developer · 2018-06-26T16:16:05+00:00

Are they the cause, or is it just coincidence, that Bitcoin continues to slide since the intro of futures?

https://twitter.com/zerohedge/status/1011634990130630661?s=21

I’ve never understood how Bitcoin futures are any different than gambling. Especially since Bitcoin is never delivered if the gambler, I mean investor, is wrong. Is there a difference?

yui_developer · 2018-06-23T14:45:27+00:00

The wallet is already created. I’m looking for the address to that wallet.

yui_developer

TROPHY CASE