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

Version 0.2.0 #11

Closed
wants to merge 8 commits into from
Closed

Version 0.2.0 #11

wants to merge 8 commits into from

Conversation

graphemecluster
Copy link
Member

待實現功能參見 #10

可以在這裏試用:https://graphemecluster.github.io/qieyun-autoderiver/

目前依靠 https://github.com/graphemecluster/qieyun-autoderiver-evaluate

先試試看,適配好 0.13 後沒問題就可以發佈了(不用等 #10 的功能全部實現)。

@syimyuzya
Copy link
Member

好耶!

@syimyuzya
Copy link
Member

對了話說那個 require 是要怎樣使用的呀?

@graphemecluster
Copy link
Member Author

require 是用來擴展既有推導方案的,我待會兒寫個例子~

@graphemecluster graphemecluster marked this pull request as draft May 6, 2022 02:52
@graphemecluster
Copy link
Member Author

↑ 適配好 0.13 之後再轉回來~

@syimyuzya
Copy link
Member

syimyuzya commented May 6, 2022

先試試看,適配好 0.13 後沒問題就可以發佈了

對了,雖然說過最好和 qieyun-examples 的 API 統合,但推導器也可以直接在用上 Qieyun 0.13 的資料後就先行上線,之後再統合w

(估了一下 qieyun-examples(即 Qieyun.推導方案)工作量後的結論w

@syimyuzya
Copy link
Member

syimyuzya commented May 13, 2022

適配好 0.13

啊對了~還有個要注意的點:

一些推導方案尚未適配 0.13,那些方案的選項列表裡都會有一項 ['$legacy', true],這個不要當成選項,要當成「標示其為 0.12 時代舊方案」的意思,給它們傳 音韻地位 前要對其做以下處理:

// 預先定義:
import { 表達式, 適配分析體系 } from 'qieyun';
const 適配poem = 適配分析體系('poem');

// 傳給舊方案前:
地位 = 適配poem(地位);
if (地位.屬於`脣音 或 ${表達式.開合中立韻}`) 地位 = 地位.調整({ : null });
if (!地位.屬於`${表達式.重紐母} (${表達式.重紐韻} 或 清韻)`) 地位 = 地位.調整({ 重紐: null });

【↑代碼引自 qieyun-js 原本打算為推導器和 qieyun-examples 準備的共用 API

@syimyuzya
Copy link
Member

由於 unt 的新版《聲音唱和圖》方案很快就會發佈,將基於 v0.13 的 Qieyun.js,為了便於公開使用,原界面已經升級為使用 v0.13 了。

新界面版本的話,應該可以跳過適配 Qieyun.js v0.13,直接與(開發中的)v0.14 相配合了w

graphemecluster and others added 3 commits August 22, 2022 18:33
Now it shows the Error's `.message` (as well as messages from the cause
chain) in addition to the stack trace, makes it much easier to know
what's wrong in the schema code.
Show `.message` in the error message box
@syimyuzya
Copy link
Member

See #20 (comment)

@syimyuzya syimyuzya closed this Aug 3, 2024
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.

4 participants