hoge を正しく機能させるために fugoFilter などを
カスタムして bar を有効にさせようと思っています.
どなたかこのカスタムの影響を教えていただけないでしょうか?
以下の2点のカスタムを考えています.
・xmlにbarの記述を許可する
・bar=falseとした場合はfugoFilterが呼ばれるようにする.
そもそもbarが非推奨になった理由を教えていただけると助かります.
また次バージョンでは,barが完全に廃止になっている理由も教えていだけると助かります.
翻訳 / 英語
- 2016/06/20 02:23:48に投稿されました
I want to enable the bar by customizing fugofilter to get hoge to function correctly.
Will someone tell me what affects of this customization would be?
The following is customization I am thinking of.
・allows xml to write about bar
・if bar=false, fugoFilter will be called
It would be helpful if you could tell me why bar became not to be recommended in the first place.
Also, it would be helpful if you could tell me why bar will be eliminated completely for the next version.
Will someone tell me what affects of this customization would be?
The following is customization I am thinking of.
・allows xml to write about bar
・if bar=false, fugoFilter will be called
It would be helpful if you could tell me why bar became not to be recommended in the first place.
Also, it would be helpful if you could tell me why bar will be eliminated completely for the next version.
翻訳 / 英語
- 2016/06/20 02:10:19に投稿されました
I am planning to activate bar by customizing fugoFilter and others in order to make hoge work properly.
Can anyone tell me about the impact of such customizing?
I am planning two kinds of customizing mentioned below.
- To allow xml to specify bar.
- To make fugoFilter is called in case of bar=false.
I would appreciate if you can tell me the reason bar is not recommended any more in the first place.
And, I also appreciate why bar is completely deprecated in the next version.
Can anyone tell me about the impact of such customizing?
I am planning two kinds of customizing mentioned below.
- To allow xml to specify bar.
- To make fugoFilter is called in case of bar=false.
I would appreciate if you can tell me the reason bar is not recommended any more in the first place.
And, I also appreciate why bar is completely deprecated in the next version.