In my testing intellisense worked whether I used any prefix or no prefix. The logic the intellisense code uses to determine what prefix to use looks for a prefix in the schema tag. If there is a prefix in the schema tag, the logic uses that prefix for all the non-dfdl elements. If there is no prefix on the schema element, or there is no schema element, the logic doesn't use a prefix.
These are the two test I performed: Test 1: <?xml version="1.0" encoding="UTF-8"?> <schema xmlns:xs="http://www.w3.org/2001/xmlSchema"; xmlns:dfdl="http://www.ogf.org/dfdl/dfdl-1.0/"; xmlns:daf="urn:ogf:dfdl:2013:imp:daffodil.apache.org:2018:ext" xmlns:fn="http:/www.w3.org/2005/xpath-functions" elementFormDefault="unqualified"> <sequence> <element name="foo" type="xs:string" dfdl:length="25"> </element> </sequence> </schema> Test 2: <sequence> <element name="foo" dfdl:lengthKind="fixed" dfdl:length="25"> </element> </sequence> Note: In the first test I used intellisense to autocomplete all the lines. In the second test I deleted all the lines except the sequence open and close tags then used intellisense to insert the element tag and the attributes. Can you provide an example of your test where intellisense did not work? Thanks, Regis Thomas -----Original Message----- From: Steve Lawrence <[email protected]> Sent: Friday, April 28, 2023 3:54 PM To: [email protected] Subject: Re: [VOTE] Apache Daffodil VS Code Extension 1.3.0-rc1 -1 (binding) Checks I marked as MINOR and I'm fine with them being fixed prior to the release or in the next release. However, considering Mike B's -1, I've marked the LICENSE/NOTICE issues as FAILED and suggest they be fixed along with fixes to resolve the issue Mike Found. I checked: [OK] hashes and signatures of source and helper binaries are correct [OK] signature of git tag is correct [OK] source release matches git tag [OK] source compiles using yarn package [OK] tests pass using yarn test [OK] RAT check passes [OK] no unexpected binaries in source [OK] vsix installs without error [OK] Page for release candidate published on website [MINOR] intellisense autocompletion - Autocompletion does not work for schemas that do not use the xs: prefix. I think this is a known issue, but tripped me up. Hopefully there is a plan to fix this in the future as more and more schemas are written without xs: prefix - Missing xs:group completion as a child of xs:sequence - Autocompletion as a child of xs:schema suggests things that aren't allowed (e.g. group ref, choice, element ref) - Do not get dfdl:defineFormat,dfdl:defineEscapeSchema after dfdl:format tag [MINOR] compiled source matches convenience binary exactly (except for timestamps in daffodil-debugger zip/jar) - The Appinfo.class file in daffodil-debugger jar is different from the same file in a custom built .vsix file. It's not clear to me what is different but this makes reproducible builds difficult to verify and is a bit concerning. I don't know why this file would be different. I'm guessing this is a JAXB thing and is autogenerated and has some variability to it? [MINOR] No open CVE's found using sbt-dependency-check plugin and yarn audit (except for false positives) - CVE's related to Apache Ant, is this a false positive? I don't know why we would be using Ant but dependencyCheck thinks we do [MINOR] no closed issues without a milestone - There are a handful of issues that have been closed but have not been assigned a milestone. Were they closed as part of 1.3.0? Can they be added to this milestone so there's a record of what release fixed the issue? https://usg02.safelinks.protection.office365.us/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fdaffodil-vscode%2Fissues%3Fq%3Dis%253Aissue%2Bis%253Aclosed%2Bno%253Amilestone&data=05%7C01%7Cregis.thomas%40nteligen.com%7C9101fb94078b438041ac08db48226146%7C379c214c5c944e86a6062d047675f02a%7C0%7C0%7C638183084742657772%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=swITmbLbUsNfvO%2FMFL4lkyTDO%2FtZKnYRLM6Z6jzgQ74%3D&reserved=0 [FAILED] src and binaries include correct LICENSE/NOTICE - build/extension.webpack.config.js is MIT licenses but is not in the main LICENSE file. It is in build/package/LICENSE file, but I think that is incorrect since this file does not end up in the vsix file? - The following yarn dependencies are listed as production dependencies but are not listed in the build/package/LICENSE file. They are category A so are okay but need to be listed: BSD-3-Clause - [email protected] ISC - [email protected] MIT - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - The following dependencies are listed in build/package/LICENSE or biuld/package/NONOTICE but are not actual production dependencies and should not be listed: - @cspotcode/source-map-support - @jridgewell/resolve-uri - @jridgewell/sourcemap-codec - @jridgewell/trace-mapping - @tsconfig/node10 - @tsconfig/node12 - @tsconfig/node14 - @tsconfig/node16 - acorn - acorn-walks - arg - create-require - diff - fsevents - is-fullwidth-code-point - make-error - ts-node - v8-compile-cache-lib - yn - The build/production/LICENSE file lists omega-edit-grpc-server-*.zip but that ZIP is no longer in the vsix file, the zip is packages uncompressed - The build/package/ licenes files mention akka, though that has been replaced with pekko - The following omega-edit or daffodil debugger jar dependencies are not mentioned in the build/package/* files Daffodil Debugger: - com.sun.istack.istack-commons-runtime-2.21.jar - com.sun.istack.istack-commons-tools-2.21.jar - com.sun.xml.bind.external.rngom-2.2.11.jar - com.sun.xml.bind.jaxb-impl-2.2.11.jar - com.sun.xml.dtd-parser.dtd-parser-1.1.jar - com.sun.xsom.xsom-20140925.jar - javax.activation.activation-1.1.1.jar - javax.xml.bind.jaxb-api-2.2.12-b140109.1041.jar - org.apache.ant.ant-1.7.0.jar - org.apache.ant.ant-launcher-1.7.0.jar - org.glassfish.jaxb.codemodel-2.2.11.jar - org.glassfish.jaxb.jaxb-core-2.2.11.jar - org.glassfish.jaxb.jaxb-xjc-2.2.11.jar - org.glassfish.jaxb.txw2-2.2.11.jar - relaxngDatatype.relaxngDatatype-20020414.jar Omega Edit - ch.qos.logback.logback-classic-1.3.5.jar - ch.qos.logback.logback-core-1.3.5.jar - com.google.api.grpc.proto-google-common-protos-2.9.0.jar - org.checkerframework.checker-qual-3.12.0.jar - org.parboiled.parboiled_2.13-2.4.1.jar On 2023-04-25 02:00 PM, Shane Dell wrote: > Hello all,I'd like to call a vote to release Apache Daffodil VS Code > 1.3.0-rc1. > > All distribution packages, including signatures, digests, etc. can be > found at: > https://usg02.safelinks.protection.office365.us/?url=https%3A%2F%2Fdis > t.apache.org%2Frepos%2Fdist%2Fdev%2Fdaffodil%2Fdaffodil-vscode%2F1.2.0 > -rc3%2F&data=05%7C01%7Cregis.thomas%40nteligen.com%7C9101fb94078b43804 > 1ac08db48226146%7C379c214c5c944e86a6062d047675f02a%7C0%7C0%7C638183084 > 742657772%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIi > LCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=9xdAAXaGmPwVu8oBz > dx3BmA7Ug1%2Fb2NTHL96N7SEA%2Fw%3D&reserved=0 > > This release has been signed with PGP key > 86DDE7B41291E380237934F007570D3ADC76D51B, corresponding to > [email protected], which is included in the KEYS file here: > https://usg02.safelinks.protection.office365.us/?url=https%3A%2F%2Fdow > nloads.apache.org%2Fdaffodil%2FKEYS&data=05%7C01%7Cregis.thomas%40ntel > igen.com%7C9101fb94078b438041ac08db48226146%7C379c214c5c944e86a6062d04 > 7675f02a%7C0%7C0%7C638183084742657772%7CUnknown%7CTWFpbGZsb3d8eyJWIjoi > MC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7 > C%7C&sdata=XbmQKLrhqTW5RDSc2z%2BTXJK%2BHxEW1v3kKq7JTfzE448%3D&reserved > =0 > > The release candidate has been tagged in git with 1.3.0-rc1. > > For reference, here is a list of all closed GitHub issues tagged with 1.3.0: > https://usg02.safelinks.protection.office365.us/?url=https%3A%2F%2Fgit > hub.com%2Fapache%2Fdaffodil-vscode%2Fmilestone%2F4%3Fclosed%3D1&data=0 > 5%7C01%7Cregis.thomas%40nteligen.com%7C9101fb94078b438041ac08db4822614 > 6%7C379c214c5c944e86a6062d047675f02a%7C0%7C0%7C638183084742657772%7CUn > known%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haW > wiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=TUpYxTGOPXw1nryCDjzuytdV9egpkPA > MQUUt6N6dgMk%3D&reserved=0 > > Please review and vote. The vote will be open for at least 72 hours > (Friday, 28 April 2023, 2:00pm EST). > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > Please note one of the large features that was focused on in 1.3.0 was > improving the data editor. To open the data editor you will need to > open the command palette using: > > - Ctrl + Shift + P (windows/linux) > - Command + Shift + P (mac) > > Then typing "data.edit", make sure "Daffodil Debug: Data Editor" is > selected and then hitting enter. By default the data editor will run > on port 9000 of your machine. However, if you want to use a different > port you can add > "dataEditor.omegaEditPort": 9001 to your vscode/launch.json configuration. > Then once you run the command again the data editor should now use port 9001. > > Thank you, > > - Shane Dell >
