Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
xxadev
jenkins
提交
a5ca50d0
J
jenkins
项目概览
xxadev
/
jenkins
与 Fork 源项目一致
从无法访问的项目Fork
通知
3
Star
0
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
J
jenkins
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
a5ca50d0
编写于
6月 03, 2013
作者:
K
Kohsuke Kawaguchi
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
did some more experiments only to hit additional problems
上级
46f603d2
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
47 addition
and
0 deletion
+47
-0
core/src/main/resources/dsld/IntelliJ.gdsl
core/src/main/resources/dsld/IntelliJ.gdsl
+47
-0
未找到文件。
core/src/main/resources/dsld/IntelliJ.gdsl
浏览文件 @
a5ca50d0
...
@@ -44,6 +44,53 @@ contributor(ctx) {
...
@@ -44,6 +44,53 @@ contributor(ctx) {
}
}
}
}
/*
Adding methods that'
s
not
defined
in
Java
works
,
but
trying
to
define
a
method
of
the
same
name
as
Java
doesn
't. See http://youtrack.jetbrains.com/issue/IDEA-108355
One work around that appears to work is to add a dummy 2nd parameter.
TO BE FILED:
Title: GDSL: With named parameter type information, undefined properties should be flagged
IDEA-71141 adds the named parameter support. However, I did a bit of experiments and noticed that if I
type in the parameter name that'
s
not
defined
in
the
source
code
,
IDEA
does
not
flag
it
as
undefined
.
Example
:
my
.
gdsl
:
{
code
}
contributor
(
context
(
ctype
:
"my.Foo"
))
{
def
named
=
[
parameter
(
name
:
'a'
,
type
:
Integer
),
parameter
(
name
:
'b'
,
type
:
Integer
)
]
method
name
:
"bar"
,
type
:
void
,
params
:[
args
:
named
]
}
{
code
}
something
.
groovy
:
{
code
}
Foo
foo
=
new
Foo
();
foo
.
bar
(
a
:
1
,
b
:
2
,
c
:
3
)
{
code
}
If
I
give
a
string
value
to
the
"a"
argument
,
that
gets
flagged
as
a
type
error
,
so
I
know
that
the
GDSL
definition
is
taking
an
effect
.
It
just
appears
to
be
lacking
a
validation
for
undefined
argument
names
.
In
my
humble
opinion
,
this
significantly
reduces
the
value
of
defining
named
argument
type
information
.
It
should
be
either
made
a
warning
just
like
incorrect
type
,
or
it
should
be
the
same
underscore
given
to
any
undefined
property
access
/
method
invocations
.
*/
//
experiment
contributor
(
context
(
ctype
:
"lib.FormTagLib"
))
{
def
named
=
[
parameter
(
name
:
'param1'
,
type
:
String
,
doc
:
'My doc'
),
parameter
(
name
:
'param2'
,
type
:
Integer
),
]
method
name
:
"textbox3"
,
type
:
void
,
params
:[
args
:
named
,
c
:
Closure
]
}
//
Record
of
past
experiments
//
Record
of
past
experiments
/*
/*
try
to
infer
"it"
from
the
class
name
of
Groovy
page
try
to
infer
"it"
from
the
class
name
of
Groovy
page
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录