You can use JSDoc comments to mark deprecated code:

```
/**
 * @deprecated The method should not be used
 */
export const oldFunc = () =&gt; {}
```

Also, [this eslint rule](https://github.com/gund/eslint-plugin-deprecation) can look through the deprecated methods and warn about their usage.


I had the below YAML for my Ingress and it worked (and continues to work):

```yaml
apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
  name: test-ingress
  namespace: test-layer
annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /$1
spec:
  rules:
    - host: mylocalhost.com
      http:
        paths:
          - path: /
            backend:
              serviceName: test-app
              servicePort: 5000
```

However, it tells me that it&#39;s deprecated and I should change to using `networking.k8s.io/v1`. When I do that (see below) it throws an error.

```yaml
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: test-ingress
  namespace: test-layer
annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /$1
spec:
  rules:
    - host: mylocalhost.com
      http:
        paths:
          - path: /
            backend:
              serviceName: test-app
              servicePort: 5000
```

**ERROR**
```
error: error validating &quot;test-ingress.yaml&quot;: 
  error validating data: [ValidationError(Ingress.spec.rules[0].http.paths[0].backend): 
    unknown field &quot;serviceName&quot; in io.k8s.api.networking.v1.IngressBackend, 
    ValidationError(Ingress.spec.rules[0].http.paths[0].backend): 
      unknown field &quot;servicePort&quot; in io.k8s.api.networking.v1.IngressBackend]; 
      if you choose to ignore these errors, turn validation off with --validate=false
```

Other than changing the API version, I made no other changes.

`kubectl version` returns:

```
Client Version: version.Info{Major:&quot;1&quot;, Minor:&quot;19&quot;, GitVersion:&quot;v1.19.0&quot;, GitCommit:&quot;e19964183377d0ec2052d1f1fa930c4d7575bd50&quot;, GitTreeState:&quot;clean&quot;, BuildDate:&quot;2020-08-26T14:30:33Z&quot;, GoVersion:&quot;go1.15&quot;, Compiler:&quot;gc&quot;, Platform:&quot;windows/amd64&quot;}

Server Version: version.Info{Major:&quot;1&quot;, Minor:&quot;19&quot;, GitVersion:&quot;v1.19.0&quot;, GitCommit:&quot;e19964183377d0ec2052d1f1fa930c4d7575bd50&quot;, GitTreeState:&quot;clean&quot;, BuildDate:&quot;2020-08-26T14:23:04Z&quot;, GoVersion:&quot;go1.15&quot;, Compiler:&quot;gc&quot;, Platform:&quot;linux/amd64&quot;}
```

Get error &quot;unknown field &quot;serviceName&quot; in io.k8s.api.networking.v1.IngressBackend&quot; when switch from v1beta1 to v1 in Kubernetes Ingress

I have been going round in circles with this issue, there are so many that people have issues **similar** to mine, but not one of them is the same. I am trying to get flutter fully set up, but can&#39;t resolve one of the issues.

When I run flutter `doctor -v` I get the following output:

    [√] Flutter (Channel stable, v1.12.13+hotfix.8, on Microsoft Windows [Version 10.0.18362.657], locale en-GB)
        • Flutter version 1.12.13+hotfix.8 at C:\flutter
        • Framework revision 0b8abb4724 (3 weeks ago), 2020-02-11 11:44:36 -0800
        • Engine revision e1e6ced81d
        • Dart version 2.7.0
    
    [!] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
        • Android SDK at C:\Users\%username%\AppData\Local\Android\Sdk
        • Android NDK location not configured (optional; useful for native profiling support)
        • Platform android-29, build-tools 29.0.3
        • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
        • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b04)
        X Android license status unknown.
          Try re-installing or updating your Android SDK Manager.
          See https://developer.android.com/studio/#downloads or visit https://flutter.dev/setup/#android-setup for detailed
          instructions.
    
    [√] Android Studio (version 3.6)
        • Android Studio at C:\Program Files\Android\Android Studio
        • Flutter plugin version 43.0.2
        • Dart plugin version 192.7761
        • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b04)
    
    [√] VS Code (version 1.42.1)
        • VS Code at C:\Users\%username%\AppData\Local\Programs\Microsoft VS Code
        • Flutter extension version 3.8.1
    
    [√] Connected device (1 available)
        • AOSP on IA Emulator • emulator-5554 • android-x86 • Android 9 (API 28) (emulator)
    
    ! Doctor found issues in 1 category.

And if I try to run the command flutter doctor --android-licenses I get:

&gt; Android sdkmanager tool not found
&gt; (C:\Users\%username%\AppData\Local\Android\Sdk\tools\bin\sdkmanager). Try
&gt; re-installing or updating your Android SDK, visit
&gt; https://flutter.dev/setup/#android-setup for detailed instructions.

And it&#39;s right, there is no &quot;tools&quot; folder in my SDK folder. How on earth do I fix that! I have installed all the SDK tools, even the NDK (not that flutter picks that up) I have tried creating a tools folder and copying sdkManager.bat (including the bin folder) from build-tools, but that just tells me to update my SDK manager, which when attempted just fails. 

It looks like everything still works, it just makes me a little uncomfortable having that issue there. 

Any help is much appreciated.

Flutter doctor error - Android sdkmanager tool not found. Windows

I&#39;m writing typescript definitions for a Javascript API with a deprecated method. Here&#39;s an extract of the documentation (they say API but it&#39;s just about this single method):

&gt; This API has no effect. It has been maintained for compatibility
&gt; purpose.

For compatibility purposes, I would also like to document this method in the definitions file. But if possible, I would like to communicate somehow, that it has been deprecated.

While my current issue is only about deprecation in a definitions file, I would also like to use this feature in other code. So the question is more general: How can I mark something as deprecated in typescript?

Is it possible to mark something as deprecated in typescript?

I'm writing typescript definitions for a Javascript API with a deprecated method. Here's an extract of the documentation (they say API but it's just about this single method):
> This API has no effect. It has been maintained for compatibility
> purpose.
For compatibility purposes, I would also like to document this method in the definitions file. But if possible, I would like to communicate somehow, that it has been deprecated.
While my current issue is only about deprecation in a definitions file, I would also like to use this feature in other code. So the question is more general: How can I mark something as deprecated in typescript?

Is there a way to specify a partial type in TypeScript that also makes all child objects partials as well? For example:

```js
interface Foobar {
  foo: number;
  bar: {
    baz: boolean;
    qux: string;
  };
}

const foobar: Partial&lt;Foobar&gt; = {
  foo: 1,
  bar: { baz: true }
};
```

This throws the following error:

&gt; `TS2741: Property &#39;qux&#39; is missing in type &#39;{ baz: true; }&#39; but required in type &#39;{ baz: boolean; qux: string; }&#39;.`

Is there any way to make child nodes partials as well?

TypeScript: deep partial?

Buidling the application after having upgraded dependcies to Angular 9 (and having performed necessary code changes) throws an error:  

&gt; Compiling @angular/animations : es2015 as esm2015   Compiling
&gt; @angular/animations : es2015 as esm2015   Compiling @angular/core :
&gt; es2015 as esm2015   Compiling @angular/core : es2015 as esm2015  
&gt; Compiling @angular/core : es2015 as esm2015   
&gt; **Error**: Error on worker #5: TypeError: Cannot read property &#39;fileName&#39; of null

It then goes on to throw the below error:  

&gt; Compiling @angular/core : es2015 as esm2015   Compiling
&gt; @angular/compiler/testing : es2015 as esm2015   Compiling
&gt; @angular/core : es2015 as esm2015  
&gt; **Error**: Tried to write node_modules/@angular/core/core.d.ts.__ivy_ngcc_bak with an ngcc back
&gt; up file   but it already exists so not writing, nor backing up,
&gt; node_modules/@angular/core/core.d.ts.

 
This error may be because two or more entry-points overlap and ngcc has been asked to process some files    more than once.  
You should check other entry-points in this package and set up a config to ignore any that you are not using.  

&gt; Compiling @angular/core : es2015 as esm2015   An unhandled exception
&gt; occurred: NGCC failed.

 

Angular 9 - NGCC fails with an unhandled exception

With Node.js bringing updated support for ES2020 and adding support for ES modules, how can TypeScript be configured to output JavaScript code that takes advantage of all these new features?

What TypeScript configuration produces output closest to Node.js 14 capabilities?

App fails to compile with error &lt;br/&gt;

&gt; error NG6001: The class `NavigationMenuItemComponent` is listed in the declarations of the NgModule `AppModule`, but is not a directive, a component, or a pipe. Either remove it from the NgModule&#39;s declarations, or add an appropriate Angular decorator.

The error goes away when I remove the constructor with parameters. How can I resolve this whiles maintaining the constructor that has parameters, because I want to use to initialise a list of the component without having to call set methods for each member in the list

    import {
        Component,
        OnInit
    } from &#39;@angular/core&#39;;

    @Component({
        selector: &#39;app-navigation-menu-item&#39;,
        templateUrl: &#39;./navigation-menu-item.component.html&#39;,
        styleUrls: [&#39;./navigation-menu-item.component.scss&#39;]
    })
    export class NavigationMenuItemComponent implements OnInit {
        static readonly ID_PREFIX: string = &#39;sidebar-menuitem-&#39;;
        static readonly ICON_CLASS_PREFIX: string = &#39;mdi mdi-&#39;;

        constructor(id: string, iconClass: string) {
            this._id = NavigationMenuItemComponent.ID_PREFIX + id;
            this._iconClass = NavigationMenuItemComponent.ICON_CLASS_PREFIX + iconClass;
        }
        //constructor() {}

        private _id: string;
        private _iconClass: string;

        get id() {
            return this._id;
        }

        get iconClass() {
            return this._iconClass;
        }

        set id(id: string) {
            this._id = NavigationMenuItemComponent.ID_PREFIX + id;
        }

        set iconClass(iconClass) {
            this._iconClass = NavigationMenuItemComponent.ID_PREFIX + iconClass;
        }

        ngOnInit(): void {}
    }


Angular Compile Error: NG6001: The class is listed in the declarations of the NgModule &#39;AppModule&#39;, but is not a directive, a component, or a pipe

I have a simple file `types.ts` that defines some types:

    export interface MyInterface {
       // ...
    }
    
    export const enum MyEnum {
       // ...
    }
    
    export type MyType = {
      // ...
    }

I have read about the new feature `import type` for the latest typescript [here][1]. As far as I understand it is meant to fix specific problems which seems mostly to happen when importing from .js files.

I can import my types with both `import` and `import type` statements. Both seems to work equally fine. The question is should I prefer `import type` for being more explicit and helping me to avoid some theoretical edge-case problems or can I just use `import` for simplicity and rely on `import elision` to remove these from compiled code?

In other words: is there any benefit of using `import type` here or it should rather be used for specific cases to work around `import elision` shortcomings?

  [1]: https://devblogs.microsoft.com/typescript/announcing-typescript-3-8-beta/#type-only-imports-exports

Do I need to use the &quot;import type&quot; feature of TypeScript 3.8 if all of my imports are from my own file?

I&#39;m new to React and I&#39;m learning about the React component lifecycle with the latest version of React. My &quot;super&quot; call of the partial code below is flagged with the deprecated warning shown. I&#39;ve had trouble understanding this one, as a lot of documentation out there still uses &quot;super&quot;, and I&#39;m not sure what the successor is, even from the full article linked in the feedback. Any ideas? Thanks.

    class App extends Component {
      constructor(props) {
        super(props);
      }
    }

Here is the warning:
```reactjs
constructor React.Component&lt;any, any, any&gt;(props: any, context?: any): React:Component&lt;any, any, any&gt; (+1 overload)
@deprecated
@see - https://reactjs.org/docs/legacy-context.html
&#39;(props: any, context?: any): Component&lt;any, any, any&gt;&#39; is deprecated ts(6385)
```

Understanding why super() is deprecated in a React class component

[![Deprecaated][1]][1]
According to [Official Android Documentation][2] Deprecated itself is deprecated in API level S. So what&#39;s the replacement for Deprecated which itself is deprecated?

Edit: Added web archive [link][3] for historical reference. 


  [1]: https://i.stack.imgur.com/U2JFj.png
  [2]: https://developer.android.com/reference/java/lang/Deprecated
  [3]: https://web.archive.org/web/20210218192448/https://developer.android.com/reference/java/lang/Deprecated

Android Deprecated Annotation is deprecated, what&#39;s the replacement?

I tried to implement request permissions for writing and reading from storage. Everything worked good but today Android showed me that the method onRequestPermissionsResult(...) is deprecated. There are so many questions about this topic in StackOverflow, but unfortunately, they are outdated. 

I called the methods below in a fragment. 

It was suggested simply to call:

    requestPermissions(new String[] {Manifest.permission.WRITE_EXTERNAL_STORAGE},
    StorageKeys.STORAGE_PERMISSION_CODE)

instead of my approach:

    ActivityCompat.requestPermissions(getActivity(),
    new String[] {Manifest.permission.WRITE_EXTERNAL_STORAGE},
    StorageKeys.STORAGE_PERMISSION_CODE))

But both of them show that onRequestPermissionsResult(...) is deprecated.

Here is my onRequestPermissionsResult(...)-method:

      @Override
      public void onRequestPermissionsResult(int requestCode, @NonNull String[] permissions,
                                             @NonNull int[] grantResults) {
    
        if (requestCode == StorageKeys.STORAGE_PERMISSION_CODE) {
    
          if (grantResults.length &gt; 0
              &amp;&amp; grantResults[0] == PackageManager.PERMISSION_GRANTED) {
    
            exportBibTex.createBibFile();
            exportBibTex.writeBibFile(exportBibTex
                .getBibDataLibrary(libraryModel, bookDao, noteDao));
    
            Toast.makeText(getContext(),
                getString(R.string.exported_file_stored_in) + &#39;\n&#39;
                    + File.separator + StorageKeys.DOWNLOAD_FOLDER + File.separator + fileName
                    + StorageKeys.BIB_FILE_TYPE, Toast.LENGTH_LONG).show();
    
          } else {
            Toast.makeText(getContext(), R.string.storage_permission_denied,
                Toast.LENGTH_SHORT).show();
          }
        }
      }

Here is a simple alert dialog, in which I call the onRequestPermissionsResult(...):

      private void showRequestPermissionDialog() {
        AlertDialog.Builder reqAlertDialog = new AlertDialog.Builder(getContext());
        reqAlertDialog.setTitle(R.string.storage_permission_needed);
        reqAlertDialog.setMessage(R.string.storage_permission_alert_msg);
    
        reqAlertDialog.setPositiveButton(R.string.ok,
            (dialog, which) -&gt; ActivityCompat.requestPermissions(getActivity(),
                new String[] {Manifest.permission.WRITE_EXTERNAL_STORAGE},
                StorageKeys.STORAGE_PERMISSION_CODE));
        reqAlertDialog.setNegativeButton(R.string.cancel,
            (dialog, which) -&gt; dialog.dismiss());
    
        reqAlertDialog.create().show();
      }

Is there any alternative for onRequestPermissionsResult(...), that I can use?

Android - onRequestPermissionsResult() is deprecated. Are there any alternatives?

I have a simple ReactJS app based on hooks (no classes) using StrictMode. 

I am using React version 16.13.1 and Material-UI version 4.9.10.

In the Appbar I am using Drawer. 

        &lt;div className={classes.root}&gt;
            &lt;AppBar position=&quot;static&quot;&gt;
                &lt;Toolbar&gt;
                    &lt;IconButton
                        edge=&quot;start&quot;
                        className={classes.menuButton}
                        color=&quot;inherit&quot;
                        aria-label=&quot;menu&quot;
                        onClick={handleDrawerOpen}&gt;
                        &lt;MenuIcon /&gt;
                    &lt;/IconButton&gt;
                    &lt;Typography variant=&quot;h6&quot; className={classes.title}&gt;
                        Online Information
                    &lt;/Typography&gt;
                &lt;/Toolbar&gt;
            &lt;/AppBar&gt;
            &lt;Drawer
                variant=&quot;persistent&quot;
                anchor=&quot;left&quot;
                open={open}
            &gt;&lt;/Drawer&gt;
        &lt;/div&gt;

I notice that when I open the Drawer, I get the following warning.

    Warning: findDOMNode is deprecated in StrictMode. findDOMNode was passed an instance 
    of 
    Transition which is inside StrictMode. Instead, add a ref directly to the element you 
    want to reference. Learn more about using refs safely ....
    in div (created by Transition)
    in Transition (created by ForwardRef(Fade))
    in ForwardRef(Fade) (created by ForwardRef(Backdrop))
    in ForwardRef(Backdrop) (created by WithStyles(ForwardRef(Backdrop)))
    in WithStyles(ForwardRef(Backdrop)) (created by ForwardRef(Modal))
    in div (created by ForwardRef(Modal))
    in ForwardRef(Portal) (created by ForwardRef(Modal))
    in ForwardRef(Modal) (created by ForwardRef(Drawer))
    in ForwardRef(Drawer) (created by WithStyles(ForwardRef(Drawer)))
I found some reference on the web for this issue but still can’t figure out how to resolve this issue.

Can someone please add some workaround for this problem?

Thank you 


material-ui Drawer - findDOMNode is deprecated in StrictMode

I am using mongoose and mocha for MongoDB schema design and API development
I am getting this warning...
what does this mean, how it will affect me and what is the fix??

Below the actual warning text:

&gt;(node:9872) DeprecationWarning: Listening to events on the Db class has been deprecated and will be removed in the next major version.

Content Type	Original Author	Original Content on Stackoverflow
Question	lhk	View Question on Stackoverflow
Solution 1 - Typescript	Vladyslav Zavalykhatko	View Answer on Stackoverflow

Is it possible to mark something as deprecated in typescript?

Typescript Problem Overview

Typescript Solutions

Solution 1 - Typescript

Flutter doctor error - Android sdkmanager tool not found. Windows

Get error "unknown field "serviceName" in io.k8s.api.networking.v1.IngressBackend" when switch from v1beta1 to v1 in Kubernetes Ingress

Attributions