[roll] Roll fuchsia [fidl] Remove @available legacy argument This removes the @available argument 'legacy' from all .fidl files, and removes support from it in fidlc, since it is obsoleted by RFC-0232 (targeting multiple API levels). Some background: * Before, FIDL authors used @available(removed=N, legacy=true) to implement APIs in the platform at the special API level LEGACY. * Since I79c264efdc4ae1cbb545f7be6862180a4cfbffb4, fidlc has enforced legacy=true and legacy=false based on the set of supported API levels passed to it, e.g. `--available fuchsia:15,16,17,18,19,20,21,HEAD`. * With this CL, fidlc no longer allows 'legacy' arguments in .fidl source, and infers them instead. Internally, fidlc still refers to the combined set of target API levels as LEGACY, because it is still modeled as HEAD + re-adding things that were removed. A follow up will remove that restriction and all remnants of the "legacy" idea, completing the transition to the RFC-0232 model. Test: fx test fidlc-test Original-Bug: 42085274 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1062057 Original-Revision: 23720ffa9b7e2c309995352cd68609e7bdb7f951 GitOrigin-RevId: e0a640901c5d143c6f66a0deb584c3356aaac516 Change-Id: I192a99b0e79ee94dc44ea8ebd3170c663774334f
This repository contains Fuchsia's Global Integration manifest files.
All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.
Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.