michael-hoke opened a new pull request, #1414:
URL: https://github.com/apache/daffodil-vscode/pull/1414

   <!--
     Licensed to the Apache Software Foundation (ASF) under one or more
     contributor license agreements.  See the NOTICE file distributed with
     this work for additional information regarding copyright ownership.
     The ASF licenses this file to You under the Apache License, Version 2.0
     (the "License"); you may not use this file except in compliance with
     the License.  You may obtain a copy of the License at
   
         http://www.apache.org/licenses/LICENSE-2.0
   
     Unless required by applicable law or agreed to in writing, software
     distributed under the License is distributed on an "AS IS" BASIS,
     WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
     See the License for the specific language governing permissions and
     limitations under the License.
   -->
   
   Closes #1362
   
   ## Description
   
   When running a parse from a launch config and the openDataEditor flag is set 
to true, the data editor would prompt the user for the data file, even though 
it could be inferred from the launch config.
   
   Additionally, when opening the data editor via the command palette while in 
an active debug session, the user would be prompted for the data file, even 
though it could be inferred based on the config from the active debugging 
session.
   
   In both of these cases, the data editor will now infer which data file to 
open. However, when there is no active debug session, the data editor will 
still prompt the user for which file to open.
   
   ## Wiki
   
   - [ ] I have determined that no documentation updates are needed for these 
changes
   - [ ] I have added following documentation for these changes
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to