Opened 5 years ago
Last modified 3 years ago
#5911 assigned defect
NF API don't return qualified path
Reported by: | Adeel Asghar | Owned by: | Adrian Pop |
---|---|---|---|
Priority: | high | Milestone: | |
Component: | Interactive Environment | Version: | |
Keywords: | Cc: |
Description
Run the attached script. The first output of the components without -d=nfAPI
is,
{{P.M,m1,"", "public", false, false, false, false, "unspecified", "none", "unspecified",{}},{P.M,m2,"", "public", false, false, false, false, "unspecified", "none", "unspecified",{}},{P.C,c,"", "public", false, false, false, false, "unspecified", "none", "unspecified",{}}}
Note the last component P.C
.
The second output of the components with -d=nfAPI
is,
{{P.M,m1,"", "public", false, false, false, false, "unspecified", "none", "unspecified",{}},{P.M,m2,"", "public", false, false, false, false, "unspecified", "none", "unspecified",{}},{C,c,"", "public", false, false, false, false, "unspecified", "none", "unspecified",{}}}
Note that this time C
is returned. OMEdit don't like it and shows the component as not defined with a red cross.
Attachments (2)
Change History (6)
by , 5 years ago
by , 5 years ago
comment:1 by , 5 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:2 by , 4 years ago
Milestone: | 1.16.0 → 1.17.0 |
---|
comment:3 by , 4 years ago
Milestone: | 1.17.0 → 1.18.0 |
---|
Retargeted to 1.18.0 because of 1.17.0 timed release.
Note:
See TracTickets
for help on using tickets.
Retargeted to 1.17.0 after 1.16.0 release