In some cases, you do not have an alias for a specific context type, for example the p

Mayhaps an alternative would also be to have something like <div class="snippet-cl

Similar to <a class="issue-link js-issue-link" data-error-text="Failed to load title"

Yes and no. In <a class="issue-link js-issue-link" data-error-text="

Allow referencing an existing cwt configuration. about paradox-language-support HOT 3 OPEN

adriangaro commented on June 29, 2024

Allow referencing an existing cwt configuration.

from paradox-language-support.

Comments (3)

adriangaro commented on June 29, 2024

Mayhaps an alternative would also be to have something like

inline_scripts = {
  
    ## context_configs_type = multiple
    ant:governments/authorities/* = {
        ## cardinality = 0..inf
        advanced_authority_swap = cwt_config_path[authority/advanced_authority_swap]
    }
}

from paradox-language-support.

DragonKnightOfBreeze commented on June 29, 2024

Similar to #68 ?

from paradox-language-support.

adriangaro commented on June 29, 2024

Yes and no.

In #68, you inherit the context/config of the invocation place. (useful for conditional inlines)
In this, you want to inherit/copy the context/config of an existing cwt declaration. (useful for when the above is not useful/impossible to infer)

from paradox-language-support.

Related Issues (20)

Deadlock during script localization idexing HOT 2
钢铁雄心4 Expression几乎不可读
Parameters of inlines show as unused if they cannot be inferred correctly even if declared in cwt config. HOT 7
Single quotes strings seem to not be accepted by the plugin as valid, while the game does not mind them HOT 5
Parameters in cwt configs do not get auto completed if they cannot be inferred or are not present in the inline/scripted_effect etc HOT 6
`no` should be a valid value for an optional parameter in scripted effects, values and triggers. HOT 1
Allow, through cwt configs, to somehow make an inline parameter inherit the context/config of its parent/inline, specifically useful for code blocks. HOT 1
Allow specifying a trigger/effect blocks scope somehow through cwt configs if it cannot be inferred HOT 3
Typing inline_script does not show autocomplete HOT 3
Some effects change root scopes HOT 5
Paramaters that are multi line trigger blocks do not type inference correctly. HOT 5
Allow wildcard/template expression for parameter context_key HOT 1
Scripted effect not recognized, nor its cwt config. HOT 3
CTRL+B should allow moving between definition (of scripted effect, trigger, etc) and its extended cwt config if it exists HOT 2
Using `single_alias[trigger_clause]` in cwt extended definition parameters does not seem to work, nor using a multiple config type work as expected. HOT 4
Allow somehow through cwt configs to generate pseudo definitions for scripted effect, game concepts etc. HOT 3
push/replace_scope does not work on event targets HOT 1
Scope parameter that has defined type in cwt configs does not correctly switch scope if used to change scope. HOT 2
Parameters are not validated when parameter is of type scope, and the value passed is of type system_link HOT 2

Allow referencing an existing cwt configuration. about paradox-language-support HOT 3 OPEN

Comments (3)

Related Issues (20)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent