refactor(compiler): introduce InterpolationConfig#8906
refactor(compiler): introduce InterpolationConfig#8906lacolaco wants to merge 1 commit intoangular:masterfrom
InterpolationConfig#8906Conversation
c9749d4 to
0ad55cf
Compare
|
@laco0416 LGTM with some minor comments. Do you plan to amend this PR with i18n / submit a new one ? |
|
@vicb yes. I'll include i18n paraer changes.
|
InterpolationConfigInterpolationConfig
0ad55cf to
d53e98e
Compare
|
d53e98e to
191e2e1
Compare
InterpolationConfigInterpolationConfig
|
@vicb It's done. Please review again! :) |
|
Travis red is in saucelabs flaky test. |
There was a problem hiding this comment.
Dowe need to export, if not you'd better create the obj lazily
cf6a0c1 to
527d1ff
Compare
There was a problem hiding this comment.
Can I use const here?
|
@laco0416 thanks for your work. I have added a question. Could you please squash your 2 commits & rebase. |
|
thinking more about this, the symbols could not be part of the compiler config but must be part of the |
So, the compiler has |
`CompilerConfig` has a configuration of interpolation for Parser and I18nHTMLParser. `InterpolationConfig` has two properties; `startSymbol` and `endSymbol`. InterpolationRegexp of the parser will be created with its symbols.
527d1ff to
3eb2748
Compare
|
For that, we must modify the compiler system entirely. I think that is out of this PR... ;( |
Either we should revert the partial impl that is currently in master or do the full support (component based). Would you like to work on that ? We should have the feature soon if we want it in 2.0.0. However it could come in a further release. |
|
Ok, let's revert current impl. you can? |
|
Yes I'll do that. |
|
Thank you. I close here and create new PR as a feature commit. |
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
What is the current behavior? (You can also link to an open issue here)
What is the new behavior?
Does this PR introduce a breaking change?
If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
CompilerConfigtakesinterpolationarguments asInterpolationConfigtype.Other information:
ref. #8865
CompilerConfighas a configuration of interpolation for the parser.InterpolationConfighas two property;startSymbolandendSymbol.InterpolationRegexp of the parser will be created with its symbols.