checking in progress of gene-search component

apps/agora/api/src/components/teams.ts

@@ -56,11 +56,7 @@ export function sortNullProgramsForTeamsLast(teams: Team[]): void {
   });
 }
 
-export async function teamsRoute(
-  req: Request,
-  res: Response,
-  next: NextFunction,
-) {
+export async function teamsRoute(req: Request, res: Response, next: NextFunction) {
   try {
     const teams = await getTeams();
     setHeaders(res);
@@ -88,11 +84,7 @@ export async function getTeamMemberImage(name: string) {
   return files[0] || undefined;
 }
 
-export async function teamMemberImageRoute(
-  req: Request,
-  res: Response,
-  next: NextFunction,
-) {
+export async function teamMemberImageRoute(req: Request, res: Response, next: NextFunction) {
   if (!req.params || !req.params.name) {
     res.status(404).send('Not found');
     return;

libs/agora/api-client-angular/src/lib/.openapi-generator/FILES

@@ -25,6 +25,7 @@ model/gCTGeneNominations.ts
 model/gCTGeneTissue.ts
 model/gCTGenesList.ts
 model/gene.ts
+model/genesList.ts
 model/medianExpression.ts
 model/models.ts
 model/neuropathologicCorrelation.ts

libs/agora/api-client-angular/src/lib/README.md

@@ -3,14 +3,15 @@
 ### Building
 
 To install the required dependencies and to build the typescript sources run:
+
 ```
 npm install
 npm run build
 ```
 
 ### publishing
 
-First build the package then run ```npm publish dist``` (don't forget to specify the `dist` folder!)
+First build the package then run `npm publish dist` (don't forget to specify the `dist` folder!)
 
 ### consuming
 
@@ -33,25 +34,25 @@ _It's important to take the tgz file, otherwise you'll get trouble with links on
 _using `npm link`:_
 
 In PATH_TO_GENERATED_PACKAGE/dist:
+
 ```
 npm link
 ```
 
 In your project:
+
 ```
-npm link 
+npm link
 ```
 
-__Note for Windows users:__ The Angular CLI has troubles to use linked npm packages.
+**Note for Windows users:** The Angular CLI has troubles to use linked npm packages.
 Please refer to this issue https://github.com/angular/angular-cli/issues/8284 for a solution / workaround.
 Published packages are not effected by this issue.
 
-
 #### General usage
 
 In your Angular project:
 
-
 ```
 // without configuring providers
 import { ApiModule } from '';
@@ -128,9 +129,11 @@ Note: The ApiModule is restricted to being instantiated once app wide.
 This is to ensure that all services are treated as singletons.
 
 #### Using multiple OpenAPI files / APIs / ApiModules
+
 In order to use multiple `ApiModules` generated from different OpenAPI files,
 you can create an alias name when importing the modules
 in order to avoid naming conflicts:
+
 ```
 import { ApiModule } from 'my-api-path';
 import { ApiModule as OtherApiModule } from 'my-other-api-path';
@@ -150,8 +153,8 @@ export class AppModule {
 }
 ```
 
-
 ### Set service base path
+
 If different than the generated base path, during app bootstrap, you can provide the base path to your service.
 
 ```
@@ -161,6 +164,7 @@ bootstrap(AppComponent, [
     { provide: BASE_PATH, useValue: 'https://your-web-service.com' },
 ]);
 ```
+
 or
 
 ```
@@ -175,8 +179,8 @@ import { BASE_PATH } from '';
 export class AppModule {}
 ```
 
-
 #### Using @angular/cli
+
 First extend your `src/environments/*.ts` files by adding the corresponding base path:
 
 ```
@@ -187,6 +191,7 @@ export const environment = {
 ```
 
 In the src/app/app.module.ts:
+
 ```
 import { BASE_PATH } from '';
 import { environment } from '../environments/environment';
@@ -215,10 +220,11 @@ pass an arrow-function or method-reference to the `encodeParam` property of the
 (see [General Usage](#general-usage) above).
 
 Example value for use in your Configuration-Provider:
+
 ```typescript
 new Configuration({
-    encodeParam: (param: Param) => myFancyParamEncoder(param),
-})
+  encodeParam: (param: Param) => myFancyParamEncoder(param),
+});
 ```
 
 [parameter-locations-url]: https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#parameter-locations