主頁 > 軟體設計 > Vue3.0.0 is coming !

Vue3.0.0 is coming !

2020-09-25 13:30:57 軟體設計

First - Update @vue/cli

npm i @vue/cli@latest -g

Second - Look New Type

import * as vue from 'vue';
console.log(vue)
{
  BaseTransition: Object,
  Comment: Symbol(Comment),
  Fragment: Symbol(Fragment),
  KeepAlive: Object,
  Static: Symbol(Static),
  Suspense: Object,
  Teleport: Object,
  Text: Symbol(Text)
  Transition: (props, { slots }) => {},
  TransitionGroup: Object,
  callWithAsyncErrorHandling: ? callWithAsyncErrorHandling(fn, instance, type, args),
  callWithErrorHandling: ? callWithErrorHandling(fn, instance, type, args),
  camelize: (str) => {},
  capitalize: (str) => {},
  cloneVNode: ? cloneVNode(vnode, extraProps, mergeRef = false),
  compile: () => {},
  computed: ? computed(getterOrOptions),
  createApp: (...args) => {},
  createBlock: ? createBlock(type, props, children, patchFlag, dynamicProps),
  createCommentVNode: ? createCommentVNode(text = ''){}, 
  createHydrationRenderer: ? createHydrationRenderer(options),
  createRenderer: ? createRenderer(options),
  createSSRApp: (...args) => {},
  createSlots: ? createSlots(slots, dynamicSlots),
  createStaticVNode: ? createStaticVNode(content, numberOfNodes),
  createTextVNode: ? createTextVNode(text = ' ', flag = 0),
  createVNode: (...args) => {},
  customRef: ? customRef(factory),
  defineAsyncComponent: ? defineAsyncComponent(source),
  defineComponent: ? defineComponent(options),
  devtools: Object,
  getCurrentInstance: () => currentInstance || currentRenderingInstance,
  getTransitionRawChildren: ? getTransitionRawChildren(children, keepComment = false),
  h: ? h(type, propsOrChildren, children),
  handleError: ? handleError(err, instance, type, throwInDev = true),
  hydrate: (...args) => {},
  inject: ? inject(key, defaultValue, treatDefaultAsFactory = false),
  isProxy: ? isProxy(value),
  isReactive: ? isReactive(value),
  isReadonly: ? isReadonly(value),
  isRef: ? isRef(r),
  isVNode: ? isVNode(value),
  markRaw: ? markRaw(value),
  mergeProps: ? mergeProps(...args),
  nextTick: ? nextTick(fn),
  onActivated: ? onActivated(hook, target),
  onBeforeMount: (hook, target = currentInstance) => {},
  onBeforeUnmount: (hook, target = currentInstance) => {},
  onBeforeUpdate: (hook, target = currentInstance) => {},
  onDeactivated: ? onDeactivated(hook, target),
  one rrorCaptured: (hook, target = currentInstance) => {},
  onMounted: (hook, target = currentInstance) => {},
  onRenderTracked: (hook, target = currentInstance) => {},
  onRenderTriggered: (hook, target = currentInstance) => {},
  onUnmounted: (hook, target = currentInstance) => {},
  onUpdated: (hook, target = currentInstance) => {},
  openBlock: ? openBlock(disableTracking = false),
  popScopeId: ? popScopeId(),
  provide: ? provide(key, value),
  proxyRefs: ? proxyRefs(objectWithRefs),
  pushScopeId: (...),
  queuePostFlushCb: (...),
  reactive: (...),
  readonly: (...),
  ref: (...),
  registerRuntimeCompiler: (...),
  render: (...),
  renderList: (...),
  renderSlot: (...),
  resolveComponent: (...),
  resolveDirective: (...),
  resolveDynamicComponent: (...),
  resolveTransitionHooks: (...),
  setBlockTracking: (...),
  setDevtoolsHook: (...),
  setTransitionHooks: (...),
  shallowReactive: (...),
  shallowReadonly: (...),
  shallowRef: (...),
  ssrContextKey: (...),
  ssrUtils: (...),
  toDisplayString: (...),
  toHandlers: (...),
  toRaw: (...),
  toRef: (...),
  toRefs: (...),
  transformVNodeArgs: (...),
  triggerRef: (...),
  unref: (...),
  useCssModule: (...),
  useCssVars: (...),
  useSSRContext: (...),
  useTransitionState: (...),
  vModelCheckbox: (...),
  vModelDynamic: (...),
  vModelRadio: (...),
  vModelSelect: (...),
  vModelText: (...),
  vShow: (...),
  version: (...),
  warn: (...),
  watch: (...),
  watchEffect: (...),
  withCtx: (...),
  withDirectives: (...),
  withKeys: (...),
  withModifiers: (...),
  withScopeId: (...)
}

Third - Write Demo

Please refer to the notes for detailed explanation

<template>
  <div class="reactivity">
    <h3>reactivity</h3>
    {{ reactiveObj.num }}
    <button @click="handleReactivityAdd">add</button>
  </div>

  <div class="readonly">
    <h3>readonly</h3>
    {{ readonlyA.a }}
  </div>

  <div class="ref">
    <h3>ref</h3>
    {{ reactiveRef }}
    <div ref="refDiv"></div>
    <button @click="handleRefAdd">add</button>
  </div>

  <div class="toRef">
    <h3>toRef</h3>
    {{ reactiveA }}
    <button @click="handleToRefAdd">add</button>
  </div>

  <div class="toRefs">
    <h3>toRefs</h3>
    {{ b }}
    <button @click="handleToRefsAdd">add</button>
  </div>

  <div class="computed">
    <h3>computed</h3>
    {{ conputedA }}
    <button @click="handleComputedAdd">add</button>
  </div>

  <div class="customRef">
    <h3>customRef</h3>
    <input type="text" v-model="customR" />
    {{ customR }}
  </div>

  <div class="toRaw">
    <h3>toRaw</h3>
    look console
  </div>

  <!-- shallowReactive/shallowReadonly/shallowRef -->
  <div>
    <h3>shallowReactive/shallowReadonly/shallowRef</h3>
    look console
  </div>

  <!-- watch/watchEffect -->
  <div class="watch">
    <h3>watch/watchEffect</h3>
    <button @click="handleChange">click and look console</button>
  </div>

  <div class="nextTick">
    <h3>nextTick</h3>
    {{ reactiveNextTickObj.a }}
    <button @click="handleNextTickChange">add and look console</button>
  </div>

  <!-- provide/inject -->
  <div>
    <h3>provide/inject</h3>
    look console
  </div>

  <div class="getCurrentInstance">
    <h3>getCurrentInstance</h3>
    look console
  </div>
</template>

<script>
import { reactive, readonly, ref, onMounted, toRef, toRefs, computed, customRef, toRaw, isReactive, shallowReactive, shallowReadonly, 
shallowRef, watch, watchEffect, nextTick, provide, inject, getCurrentInstance } from 'vue';
export default {
  setup() {
    // reactivity: Receives a normal object and returns the responsive proxy for that common object
    let reactiveObj = reactive({ num: 1, a: 1, b: 2, c: 3 });
    const handleReactivityAdd = () => { reactiveObj.num += 1; };

    // readonly: Gets an object (responsive or pure) or ref and returns the read-only proxy of the original agent. Read only proxies are deep: any nested properties accessed are also read-only.
    const readonlyA = readonly({ a: 1 });
    readonlyA.a += 2;
    // Set operation on key "a" failed: target is readonly. { a: 1 }

    // ref: Accepts the parameter and returns it wrapped in an object with a value property, which can then be used to access or change the value of the response variable, and on components or elements that can also function
    let reactiveRef = ref(0);
    let refDiv = ref(0);
    const handleRefAdd = () => { reactiveRef.value += 1 };
    let handleMounted = async () => { console.log(refDiv) };
    onMounted(handleMounted);

    // toRef: Can be used to create a ref for properties on source responsive objects. You can then pass the ref out to maintain a responsive connection to its source property.
    const reactiveA = toRef(reactiveObj, 'a');
    const handleToRefAdd = () => { reactiveA.value += 1 };

    // toRefs: Convert a responsive object to a normal object, where each property of the result object is a ref pointing to the corresponding property of the original object.
    const handleToRefsAdd = () => { reactiveObj.b += 1 };

    // computed: Like ref and watch, you can use the computed functions imported from Vue to create calculated properties outside the Vue component.
    const conputedA = computed(() => reactiveObj.c + 2);
    const handleComputedAdd = () => { reactiveObj.c += 1 };

    // customRef: Create a custom ref and explicitly control its dependency tracking and update triggering. It needs a factory function that takes the track and trigger functions as parameters and should return an object with get and set.
    const handleCustom = ( value, delay = 1000 ) => {
      let timeout;
      return customRef((track, trigger) => {
        return {
          get() {
            track();
            return value;
          },
          set(newValue) {
            clearTimeout(timeout);
            timeout = setTimeout(() => {
              value = newValue;
              trigger();
            }, delay)
          }
        }
      })
    }

    // toRaw: Returns the original object of the reactive or readonly proxy. This is an escape port that can be used for temporary read without proxy access / trace overhead, or for writing without triggering changes. It is not recommended to keep a persistent reference to the original object. Please use with caution.
    const obj = {};
    const reactiveToRawObj = reactive(obj);
    console.log('toRaw------' + (toRaw(reactiveToRawObj) === obj));            // true

    // shallowReactive/shallowReadonly/shallowRef:
    
    // Shadowreactive creates a responsive proxy that tracks the responsiveness of its own properties, but does not perform deep responsive conversions of nested objects (exposing the original values).
    
 	// Shallowreadonly creates a proxy with its own property read-only, but does not perform deep read-only conversion of nested objects (exposing the original values).
 	
	// Shadowref creates a ref that tracks its own. Value changes, but does not make its value responsive.
    const shallowObj = shallowReactive({
      a: '123',
      b: {
        c: 456
      }
    });
    const readonlyShallowObj = shallowReadonly({
      a: '123',
      b: {
        c: 456
      }
    });
    const shallowRefObj = shallowRef(0);

    console.log('shallowReactive------' + isReactive(shallowObj.b));           // false
    console.log('shallowReadonly------' + isReactive(readonlyShallowObj.b));   // false
    console.log('shallowRef------' + isReactive(shallowRefObj.value));         // false

    // watch/watchEffect:

	// Watch needs to listen to a specific data (responsive) source and have side effects in a separate callback function. By default, it is also inert -- that is, callbacks are called only when the listening source changes.
	
	// Watcheffect immediately runs a function when it tracks its dependencies responsibly and reruns it when the dependency changes.
    let reactiveObjA = reactive({ a: 1 });
    let reactiveObjB = reactive({ b: 1 });
    const handleChange = () => {
      reactiveObjA.a += 1;
      reactiveObjB.b += 1;
    };
    watchEffect(() => {
      console.log('reactiveObjA.a------' + reactiveObjA.a)
      console.log('reactiveObjB.b------' + reactiveObjB.b)
    })
    watch(
      [() => reactiveObjA.a, () => reactiveObjB.b],
      ([newA, newB], [a, b]) => {
        console.log('newA------' + newA);
        console.log('newB------' + newB);
        console.log('a------' + a);
        console.log('b------' + b);
      }
    )

    // nextTick: Postpone the callback until after the next DOM update cycle. Use it as soon as you have changed some data to wait for the DOM to update.
    const reactiveNextTickObj = reactive({ a: 1 });
    const handleNextTickChange = async () => {
      reactiveNextTickObj.a += 1;
      await nextTick();
      console.log('dom is uodated')
    }

    // provide/inject: Provide and inject enable dependency injection. Both can be called only during setup () using the current active instance.
    provide('a', 1);
    const a = inject('a');
    console.log('provide/inject------' + a)

    // getCurrentInstance: Gets an instance of the current component, similar to this of 2.0
    const { ctx } = getCurrentInstance();
    console.log('getCurrentInstance------')
    console.log(ctx)

    // createApp/createSSRApp
    // createApp(App).use(store).use(router).mount('#app');

    return {
      reactiveObj,
      handleReactivityAdd,
      readonlyA,
      reactiveRef,
      handleRefAdd,
      refDiv,
      handleMounted,
      reactiveA,
      handleToRefAdd,
      handleToRefsAdd,
      ...toRefs(reactiveObj),
      conputedA,
      handleComputedAdd,
      customR: handleCustom(''),
      handleChange,
      reactiveNextTickObj,
      handleNextTickChange
    };
  }
}
</script>

<style scoped>
  h3 {
    color: rgb(177, 12, 12);
  }
</style>

轉載請註明出處,本文鏈接:https://www.uj5u.com/ruanti/125853.html

標籤:其他

上一篇:【快應用】選單遮擋內容?教你一招快速搞定!

下一篇:SpringBoot-web開發(三): 模板引擎Thymeleaf

標籤雲
其他(157675) Python(38076) JavaScript(25376) Java(17977) C(15215) 區塊鏈(8255) C#(7972) AI(7469) 爪哇(7425) MySQL(7132) html(6777) 基礎類(6313) sql(6102) 熊猫(6058) PHP(5869) 数组(5741) R(5409) Linux(5327) 反应(5209) 腳本語言(PerlPython)(5129) 非技術區(4971) Android(4554) 数据框(4311) css(4259) 节点.js(4032) C語言(3288) json(3245) 列表(3129) 扑(3119) C++語言(3117) 安卓(2998) 打字稿(2995) VBA(2789) Java相關(2746) 疑難問題(2699) 细绳(2522) 單片機工控(2479) iOS(2429) ASP.NET(2402) MongoDB(2323) 麻木的(2285) 正则表达式(2254) 字典(2211) 循环(2198) 迅速(2185) 擅长(2169) 镖(2155) 功能(1967) .NET技术(1958) Web開發(1951) python-3.x(1918) HtmlCss(1915) 弹簧靴(1913) C++(1909) xml(1889) PostgreSQL(1872) .NETCore(1853) 谷歌表格(1846) Unity3D(1843) for循环(1842)

熱門瀏覽
  • 面試突擊第一季,第二季,第三季

    第一季必考 https://www.bilibili.com/video/BV1FE411y79Y?from=search&seid=15921726601957489746 第二季分布式 https://www.bilibili.com/video/BV13f4y127ee/?spm_id_fro ......

    uj5u.com 2020-09-10 05:35:24 more
  • 第三單元作業總結

    1.前言 這應該是本學期最后一次寫作業總結了吧。總體來說,對作業的節奏也差不多掌握了,作業做起來的效率也更高了。雖然和之前的作業一樣,作業中都要用到新的知識,但是相比之前,更加懂得了如何利用工具以及資料。雖然之間卡過殼,但總體而言,這幾次作業還算完成的比較好。 2.作業程序總結 相比前兩個單元,此單 ......

    uj5u.com 2020-09-10 05:35:41 more
  • 北航OO(2020)第四單元博客作業暨課程總結博客

    北航OO(2020)第四單元博客作業暨課程總結博客 本單元作業的架構設計 在本單元中,由于UML圖具有比較清晰的樹形結構,因此我對其中需要進行查詢操作的元素進行了包裝,在樹的父節點中存盤所有孩子的參考。考慮到性能問題,我采用了快取機制,一次查詢后盡可能快取已經遍歷過的資訊,以減少遍歷次數。 本單元我 ......

    uj5u.com 2020-09-10 05:35:48 more
  • BUAA_OO_第四單元

    一、UML決議器設計 ? 先看下題目:第四單元實作一個基于JDK 8帶有效性檢查的UML(Unified Modeling Language)類圖,順序圖,狀態圖分析器 MyUmlInteraction,實際上我們要建立一個有向圖模型,UML中的物件(元素)可能與同級元素連接,也可與低級元素相連形成 ......

    uj5u.com 2020-09-10 05:35:54 more
  • 6.1邏輯運算子

    邏輯運算子 1. && 短路與 運算式1 && 運算式2 01.運算式1為true并且運算式2也為true 整體回傳為true 02.運算式1為false,將不會執行運算式2 整體回傳為false 03.只要有一個運算式為false 整體回傳為false 2. || 短路或 運算式1 || 運算式2 ......

    uj5u.com 2020-09-10 05:35:56 more
  • BUAAOO 第四單元 & 課程總結

    1. 第四單元:StarUml檔案決議 本單元采用了圖模型決議UML。 UML檔案可以抽象為圖、子圖、邊的邏輯結構。 在實作中,圖的節點包括類、介面、屬性,子圖包括狀態圖、順序圖等。 采用了三次遍歷UML元素的方法建圖,第一遍遍歷建點,第二、三次遍歷設定屬性、連邊,實作圖物件的初始化。這里借鑒了一些 ......

    uj5u.com 2020-09-10 05:36:06 more
  • 談談我對C# 多型的理解

    面向物件三要素:封裝、繼承、多型。 封裝和繼承,這兩個比較好理解,但要理解多型的話,可就稍微有點難度了。今天,我們就來講講多型的理解。 我們應該經常會看到面試題目:請談談對多型的理解。 其實呢,多型非常簡單,就一句話:呼叫同一種方法產生了不同的結果。 具體實作方式有三種。 一、多載 多載很簡單。 p ......

    uj5u.com 2020-09-10 05:36:09 more
  • Python 資料驅動工具:DDT

    背景 python 的unittest 沒有自帶資料驅動功能。 所以如果使用unittest,同時又想使用資料驅動,那么就可以使用DDT來完成。 DDT是 “Data-Driven Tests”的縮寫。 資料:http://ddt.readthedocs.io/en/latest/ 使用方法 dd. ......

    uj5u.com 2020-09-10 05:36:13 more
  • Python里面的xlrd模塊詳解

    那我就一下面積個問題對xlrd模塊進行學習一下: 1.什么是xlrd模塊? 2.為什么使用xlrd模塊? 3.怎樣使用xlrd模塊? 1.什么是xlrd模塊? ?python操作excel主要用到xlrd和xlwt這兩個庫,即xlrd是讀excel,xlwt是寫excel的庫。 今天就先來說一下xl ......

    uj5u.com 2020-09-10 05:36:28 more
  • 當我們創建HashMap時,底層到底做了什么?

    jdk1.7中的底層實作程序(底層基于陣列+鏈表) 在我們new HashMap()時,底層創建了默認長度為16的一維陣列Entry[ ] table。當我們呼叫map.put(key1,value1)方法向HashMap里添加資料的時候: 首先,呼叫key1所在類的hashCode()計算key1 ......

    uj5u.com 2020-09-10 05:36:38 more
最新发布
  • 【中介者設計模式詳解】C/Java/JS/Go/Python/TS不同語言實作

    * 中介者模式是一種行為型設計模式,它可以用來減少類之間的直接依賴關系,
    * 將物件之間的通信封裝到一個中介者物件中,從而使得各個物件之間的關系更加松散。
    * 在中介者模式中,物件之間不再直接相互互動,而是通過中介者來中轉訊息。 ......

    uj5u.com 2023-04-20 08:20:47 more
  • 露天煤礦現場調研和交流案例分享

    他們集團的資訊化公司及研究院在一個礦區正在做智能礦山的統一平臺的 試點,專案投資大概1億,包括了礦山的各方面的內容,顯示得我們這次交流有點多余。他們2年前開始做智能礦山的規劃,有很多煤礦行業專家的加持,他們的描述是非常完美,但是去年底應該上線的平臺,現在還沒有看到影子。他們確實有很多場景需求,但是被... ......

    uj5u.com 2023-04-20 08:20:25 more
  • 《社區人員管理》實戰案例設計&個人案例分享

    設計是一個讓人夢想成真程序,開始編碼、測驗、除錯之前進行需求分析和架構設計,才能保證關鍵方面都做正確 ......

    uj5u.com 2023-04-20 08:20:17 more
  • 軟體架構生態化-多角色交付的探索實踐

    作為一個技術架構師,不僅僅要緊跟行業技術趨勢,還要結合研發團隊現狀及痛點,探索新的交付方案。在日常中,你是否遇到如下問題 “ 業務需求排期長研發是瓶頸;非研發角色感受不到研發技改提效的變化;引入ISV 團隊又擔心質量和安全,培訓周期長“等等,基于此我們探索了一種新的技術體系及交付方案來解決如上問題。 ......

    uj5u.com 2023-04-20 08:20:10 more
  • 【中介者設計模式詳解】C/Java/JS/Go/Python/TS不同語言實作

    * 中介者模式是一種行為型設計模式,它可以用來減少類之間的直接依賴關系,
    * 將物件之間的通信封裝到一個中介者物件中,從而使得各個物件之間的關系更加松散。
    * 在中介者模式中,物件之間不再直接相互互動,而是通過中介者來中轉訊息。 ......

    uj5u.com 2023-04-20 08:19:44 more
  • 露天煤礦現場調研和交流案例分享

    他們集團的資訊化公司及研究院在一個礦區正在做智能礦山的統一平臺的 試點,專案投資大概1億,包括了礦山的各方面的內容,顯示得我們這次交流有點多余。他們2年前開始做智能礦山的規劃,有很多煤礦行業專家的加持,他們的描述是非常完美,但是去年底應該上線的平臺,現在還沒有看到影子。他們確實有很多場景需求,但是被... ......

    uj5u.com 2023-04-20 08:19:07 more
  • 《社區人員管理》實戰案例設計&個人案例分享

    設計是一個讓人夢想成真程序,開始編碼、測驗、除錯之前進行需求分析和架構設計,才能保證關鍵方面都做正確 ......

    uj5u.com 2023-04-20 08:18:57 more
  • 軟體架構生態化-多角色交付的探索實踐

    作為一個技術架構師,不僅僅要緊跟行業技術趨勢,還要結合研發團隊現狀及痛點,探索新的交付方案。在日常中,你是否遇到如下問題 “ 業務需求排期長研發是瓶頸;非研發角色感受不到研發技改提效的變化;引入ISV 團隊又擔心質量和安全,培訓周期長“等等,基于此我們探索了一種新的技術體系及交付方案來解決如上問題。 ......

    uj5u.com 2023-04-20 08:18:49 more
  • 05單件模式

    #經典的單件模式 public class Singleton { private static Singleton uniqueInstance; //一個靜態變數持有Singleton類的唯一實體。 // 其他有用的實體變數寫在這里 //構造器宣告為私有,只有Singleton可以實體化這個類! ......

    uj5u.com 2023-04-19 08:42:51 more
  • 【架構與設計】常見微服務分層架構的區別和落地實踐

    軟體工程的方方面面都遵循一個最基本的道理:沒有銀彈,架構分層模型更是如此,每一種都有各自優缺點,所以請根據不同的業務場景,并遵循簡單、可演進這兩個重要的架構原則選擇合適的架構分層模型即可。 ......

    uj5u.com 2023-04-19 08:42:41 more