Allow @deprecated annotation on fields in a record type

[ayeshLK]

Description:

• Developers should be able to mark a field in a record type as @deprecated.

Describe your problem(s)

• When implementing functionality in a standard library module developers usually use record types to pass required configurations. But with the API changes there might be instances where developer need to mark some configuration fields as @deprecated. Currently this is not supported in ballerina-lang.

Sample

• Standard library module 'A' has a record type a:ApiConfig which holds some configuration related to module 'A'. Now developer need to mark field1 as deprecated with the latest release.

  public type ApiConfig record {|
  @deprecated
  string field1;
  int field2;
  string[] field3;
  |};

[MaryamZi]

Moving this issue to the spec repo since the spec currently allows the @deprecated annotation only on object fields.

[ThisaruGuruge]

Is there any plan to support this? This is needed for GraphQL to fully support the @deprecate directive, which is a default directive defined by the GraphQL spec.

[chamil321]

Any update on the issue? HTTP has the same requirement to deprecate config(record) fields as new(improved) fields are being added.

[hasithaa]

Supporting this is straightforward. But I wonder, once you deprecated a field, what is the strategy to introduce a new field or a record? Because there is a possibility of the new field/record may break backward compatibility.