ide/lsp.client/apichanges.xml - netbeans - Git at Google

 <?xml version="1.0" encoding="UTF-8"?>
 <!--

     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.

 -->
 <!DOCTYPE apichanges PUBLIC "-//NetBeans//DTD API changes list 1.0//EN" "../../nbbuild/javadoctools/apichanges.dtd">
 <apichanges>
 <apidefs>
     <apidef name="lsp_client">LSP Client API</apidef>
 </apidefs>
 <changes>
     <change id="LanguageIdProvider">
         <api name="lsp_client" />
         <summary>Adding LanguageIdProvider</summary>
         <version major="0" minor="1.34" />
         <date day="27" month="2" year="2026" />
         <author login="mmatblsi" />
         <compatibility addition="yes" binary="compatible" source="compatible" />
         <description>
             <p>
                 While NetBeans uses mimetypes as primary identifier for source types,
                 LSP uses languageId as a carrier to inform what language/type of file
                 is being edited. Even a single language server can provide support
                 for multiple languages. One such example is the typescript language
                 server, which defaults to typescript, but also supports the
                 typescript variant that embeds react templates (TSX).
             </p>
             <p>
                 To support this an implementation can provide a resolver. The
                 resolver has to implement the interface
                 <code>org.netbeans.modules.lsp.client.spi.LanguageIdResolver</code>
                 and will be provided by a lookup provided to the
                 <code>LanguageServerDescription</code>. For each opened file
                 the resolver will be called with the file object and will return
                 the language id if it can resolve it for the given file.
             </p>
         </description>
         <class name="LanguageIdResolver" package="org.netbeans.modules.lsp.client.spi"/>
     </change>
     <change id="MultiMimeLanguageServerProvider">
         <api name="lsp_client" />
         <summary>Adding MultiMimeLanguageServerProvider</summary>
         <version major="0" minor="1.9" />
         <date day="22" month="2" year="2022" />
         <author login="vieiro" />
         <compatibility addition="yes" binary="compatible" source="compatible" />
         <description>
                org.netbeans.modules.lsp.client.spi.MultiMimeLanguageServerProvider
         </description>
         <class name="MultiMimeLanguageServerProvider" package="org.netbeans.modules.lsp.client.spi"/>
     </change>
     <change id="ServerRestarter">
         <api name="lsp_client" />
         <summary>Adding ServerRestarter</summary>
         <version major="0" minor="1.8"/>
         <date day="13" month="7" year="2020"/>
         <author login="jlahoda"/>
         <compatibility addition="yes" binary="compatible" source="compatible"/>
         <description>
                 org.netbeans.modules.lsp.client.spi.ServerRestarter
         </description>
         <class name="ServerRestarter" package="org.netbeans.modules.lsp.client.spi"/>
     </change>
 </changes>
 <htmlcontents>
 <head>
 <title>Change History for the LSP Client API</title>
 </head>
 <body>
 <p class="overviewlink">
 <a href="overview-summary.html">Overview</a>
 </p>
 <h1>Introduction</h1>
 <h2>What do the Dates Mean?</h2>
 <p>The supplied dates indicate when the API change was made, on the CVS
 trunk. From this you can generally tell whether the change should be
 present in a given build or not; for trunk builds, simply whether it
 was made before or after the change; for builds on a stabilization
 branch, whether the branch was made before or after the given date. In
 some cases corresponding API changes have been made both in the trunk
 and in an in-progress stabilization branch, if they were needed for a
 bug fix; this ought to be marked in this list.</p>
 <ul>
 <li>The <code>release41</code> branch was made on Apr 03 '05 for use in the NetBeans 4.1 release.
 Specification versions: 6.0 begins after this point.</li>
 <li>The <code>release40</code> branch was made on Nov 01 '04 for use in the NetBeans 4.0 release.
 Specification versions: 5.0 begins after this point.</li>
 </ul>
 <hr/>
 <standard-changelists module-code-name="$codebase"/>
 <hr/>
 <p>@FOOTER@</p>
 </body>
 </htmlcontents>
 </apichanges>
	<?xml version="1.0" encoding="UTF-8"?>
	<!--

	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.

	-->
	<!DOCTYPE apichanges PUBLIC "-//NetBeans//DTD API changes list 1.0//EN" "../../nbbuild/javadoctools/apichanges.dtd">
	<apichanges>
	<apidefs>
	<apidef name="lsp_client">LSP Client API</apidef>
	</apidefs>
	<changes>
	<change id="LanguageIdProvider">
	<api name="lsp_client" />
	<summary>Adding LanguageIdProvider</summary>
	<version major="0" minor="1.34" />
	<date day="27" month="2" year="2026" />
	<author login="mmatblsi" />
	<compatibility addition="yes" binary="compatible" source="compatible" />
	<description>
	<p>
	While NetBeans uses mimetypes as primary identifier for source types,
	LSP uses languageId as a carrier to inform what language/type of file
	is being edited. Even a single language server can provide support
	for multiple languages. One such example is the typescript language
	server, which defaults to typescript, but also supports the
	typescript variant that embeds react templates (TSX).
	</p>
	<p>
	To support this an implementation can provide a resolver. The
	resolver has to implement the interface
	<code>org.netbeans.modules.lsp.client.spi.LanguageIdResolver</code>
	and will be provided by a lookup provided to the
	<code>LanguageServerDescription</code>. For each opened file
	the resolver will be called with the file object and will return
	the language id if it can resolve it for the given file.
	</p>
	</description>
	<class name="LanguageIdResolver" package="org.netbeans.modules.lsp.client.spi"/>
	</change>
	<change id="MultiMimeLanguageServerProvider">
	<api name="lsp_client" />
	<summary>Adding MultiMimeLanguageServerProvider</summary>
	<version major="0" minor="1.9" />
	<date day="22" month="2" year="2022" />
	<author login="vieiro" />
	<compatibility addition="yes" binary="compatible" source="compatible" />
	<description>
	org.netbeans.modules.lsp.client.spi.MultiMimeLanguageServerProvider
	</description>
	<class name="MultiMimeLanguageServerProvider" package="org.netbeans.modules.lsp.client.spi"/>
	</change>
	<change id="ServerRestarter">
	<api name="lsp_client" />
	<summary>Adding ServerRestarter</summary>
	<version major="0" minor="1.8"/>
	<date day="13" month="7" year="2020"/>
	<author login="jlahoda"/>
	<compatibility addition="yes" binary="compatible" source="compatible"/>
	<description>
	org.netbeans.modules.lsp.client.spi.ServerRestarter
	</description>
	<class name="ServerRestarter" package="org.netbeans.modules.lsp.client.spi"/>
	</change>
	</changes>
	<htmlcontents>
	<head>
	<title>Change History for the LSP Client API</title>
	</head>
	<body>
	<p class="overviewlink">
	<a href="overview-summary.html">Overview</a>
	</p>
	<h1>Introduction</h1>
	<h2>What do the Dates Mean?</h2>
	<p>The supplied dates indicate when the API change was made, on the CVS
	trunk. From this you can generally tell whether the change should be
	present in a given build or not; for trunk builds, simply whether it
	was made before or after the change; for builds on a stabilization
	branch, whether the branch was made before or after the given date. In
	some cases corresponding API changes have been made both in the trunk
	and in an in-progress stabilization branch, if they were needed for a
	bug fix; this ought to be marked in this list.</p>
	<ul>
	<li>The <code>release41</code> branch was made on Apr 03 '05 for use in the NetBeans 4.1 release.
	Specification versions: 6.0 begins after this point.</li>
	<li>The <code>release40</code> branch was made on Nov 01 '04 for use in the NetBeans 4.0 release.
	Specification versions: 5.0 begins after this point.</li>
	</ul>
	<hr/>
	<standard-changelists module-code-name="$codebase"/>
	<hr/>
	<p>@FOOTER@</p>
	</body>
	</htmlcontents>
	</apichanges>