varminer-app-header 2.2.9 → 2.3.0

package/README.md

@@ -0,0 +1,93 @@
+# varminer-app-header-npm-fe
+
+
+
+## Getting started
+
+To make it easy for you to get started with GitLab, here's a list of recommended next steps.
+
+Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
+
+## Add your files
+
+- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
+- [ ] [Add files using the command line](https://docs.gitlab.com/topics/git/add_files/#add-files-to-a-git-repository) or push an existing Git repository with the following command:
+
+```
+cd existing_repo
+git remote add origin https://gitlab.medgenome.com/mgm-linc/varminer-app-header-npm-fe.git
+git branch -M main
+git push -uf origin main
+```
+
+## Integrate with your tools
+
+- [ ] [Set up project integrations](https://gitlab.medgenome.com/mgm-linc/varminer-app-header-npm-fe/-/settings/integrations)
+
+## Collaborate with your team
+
+- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
+- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
+- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
+- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
+- [ ] [Set auto-merge](https://docs.gitlab.com/user/project/merge_requests/auto_merge/)
+
+## Test and Deploy
+
+Use the built-in continuous integration in GitLab.
+
+- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/)
+- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
+- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
+- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
+- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
+
+***
+
+# Editing this README
+
+When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
+
+## Suggestions for a good README
+
+Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
+
+## Name
+Choose a self-explaining name for your project.
+
+## Description
+Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
+
+## Badges
+On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
+
+## Visuals
+Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
+
+## Installation
+Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
+
+## Usage
+Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
+
+## Support
+Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
+
+## Roadmap
+If you have ideas for releases in the future, it is a good idea to list them in the README.
+
+## Contributing
+State if you are open to contributions and what your requirements are for accepting them.
+
+For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
+
+You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
+
+## Authors and acknowledgment
+Show your appreciation to those who have contributed to the project.
+
+## License
+For open source projects, say how it is licensed.
+
+## Project status
+If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.

package/dist/index.d.ts

@@ -13,6 +13,8 @@ interface AppHeaderProps {
     language?: 'en' | 'es';
     /** When provided, used as Bearer token for profile picture and other authenticated requests. */
     accessToken?: string | null;
+    /** Base URL for the object store API (e.g. profile picture). When provided, profile picture is fetched from {objectStoreUrl}/v1/objectStore/profilePicture/path/{userId}. Omit or leave empty to disable profile picture fetch. */
+    objectStoreUrl?: string | null;
 }
 
 declare const AppHeader: React__default.FC<AppHeaderProps>;
@@ -115,13 +117,13 @@ declare const setI18nLocaleToStorage: (locale: string) => void;
  * @returns Object with auth, decodedToken, and other keys (user/userDetails/profile null when using header key)
  */
 declare const getAllDataFromStorage: () => any;
-declare const getProfilePictureUrl: (baseUrl?: string) => string | null;
+declare const getProfilePictureUrl: (baseUrl?: string | null) => string | null;
 /**
  * Get access token from all known storage keys (header, IAM, userdb, and plain keys).
  * persist:userdb shape: authDetails (stringified) contains auth.accessToken.
  */
 declare function getAccessTokenForRequest(): string | undefined;
-declare const fetchProfilePictureAsBlobUrl: (baseUrl?: string, accessTokenOverride?: string | null) => Promise<string | null>;
+declare const fetchProfilePictureAsBlobUrl: (baseUrl?: string | null, accessTokenOverride?: string | null) => Promise<string | null>;
 
 export { AppHeader, DrawerProvider, PERSIST_HEADER_KEY, USER_DETAILS_STORAGE_KEY, fetchProfilePictureAsBlobUrl, getAccessTokenForRequest, getAllDataFromStorage, getI18nLocaleFromStorage, getMessageCountFromStorage, getNotificationCountFromStorage, getProfilePictureUrl, getStoredUserDetails, getTranslations, getUserDataFromStorage, setHeaderAuth, setI18nLocaleToStorage, translations, useDrawer };
 export type { AppHeaderProps, HeaderAuthState, SupportedLanguage, Translations, UserDetailsItem, UserDetailsStoredResponse, UserProfile };

package/dist/index.esm.js

@@ -370,17 +370,20 @@ const getAllDataFromStorage = () => {
 };
 /**
  * Get profile picture URL from object store API using user_id.
- * @param baseUrl - Base URL for the object store API (default: http://objectstore.impact0mics.local:9012)
- * @returns Profile picture URL or null if user_id is not available
+ * @param baseUrl - Base URL for the object store API (e.g. from objectStoreUrl prop). When missing or empty, returns null.
+ * @returns Profile picture URL or null if user_id or baseUrl is not available
  */
 const VERIFICATION_USER_ID = 4590; // set to null to use only storage userId
-const getProfilePictureUrl = (baseUrl = "http://objectstore.impact0mics.local:9012") => {
+const getProfilePictureUrl = (baseUrl) => {
     try {
+        const url = typeof baseUrl === "string" && baseUrl.trim() ? baseUrl.trim() : null;
+        if (!url)
+            return null;
         const allData = getAllDataFromStorage();
         const userId = allData.decodedToken?.user_id ?? allData.auth?.user_id ?? getStoredUserDetails()?.userId ?? VERIFICATION_USER_ID ?? null;
         if (userId == null)
             return null;
-        return `${baseUrl.replace(/\/$/, "")}/v1/objectStore/profilePicture/path/${userId}`;
+        return `${url.replace(/\/$/, "")}/v1/objectStore/profilePicture/path/${userId}`;
     }
     catch (err) {
         console.error("Error getting profile picture URL:", err);
@@ -395,8 +398,8 @@ function getKeyFromS3Uri(s3Uri) {
 /**
  * Fetch profile picture: (1) GET path API for JSON with filePath/s3Uri, (2) GET download API with key; download returns JSON with base64 fileContent.
  * Path API: { statusResponse, filePath, s3Uri, errors }. Download API: { statusResponse, fileName, contentType, fileContent (base64), errors }.
- * @param baseUrl - Base URL for the object store API (default: http://objectstore.impact0mics.local:9012)
- * @returns Promise that resolves to blob URL string or null if fetch fails
+ * @param baseUrl - Base URL for the object store API (e.g. from objectStoreUrl prop). When missing or empty, returns null without fetching.
+ * @returns Promise that resolves to blob URL string or null if fetch fails or baseUrl not provided
  */
 /** Resolve access token from auth object (supports accessToken, access_token, token). */
 function getAccessTokenFromAuth(auth) {
@@ -522,11 +525,14 @@ function getAccessTokenForRequest() {
     }
     return getAccessTokenFromAuth(getAllDataFromStorage().auth);
 }
-const fetchProfilePictureAsBlobUrl = async (baseUrl = "http://objectstore.impact0mics.local:9012", accessTokenOverride) => {
+const fetchProfilePictureAsBlobUrl = async (baseUrl, accessTokenOverride) => {
     try {
         const profilePicturePathUrl = getProfilePictureUrl(baseUrl);
         if (!profilePicturePathUrl)
             return null;
+        const cleanBase = typeof baseUrl === "string" && baseUrl.trim() ? baseUrl.trim().replace(/\/$/, "") : "";
+        if (!cleanBase)
+            return null;
         const accessToken = (typeof accessTokenOverride === "string" && accessTokenOverride.length > 0
             ? accessTokenOverride
             : null) ?? getAccessTokenForRequest();
@@ -566,7 +572,6 @@ const fetchProfilePictureAsBlobUrl = async (baseUrl = "http://objectstore.impact
             return null;
         }
         // Step 2: GET download API → JSON with fileContent (base64) and contentType
-        const cleanBase = baseUrl.replace(/\/$/, "");
         const downloadUrl = `${cleanBase}/v1/objectStore/download?key=${encodeURIComponent(downloadKey)}`;
         const imageResponse = await fetch(downloadUrl, { method: "GET", headers });
         if (!imageResponse.ok) {
@@ -715,7 +720,7 @@ const DEFAULT_ROUTES = {
     profile: "/user/profile",
     logout: "/user/login",
 };
-const AppHeader = ({ language: languageProp, accessToken: accessTokenProp }) => {
+const AppHeader = ({ language: languageProp, accessToken: accessTokenProp, objectStoreUrl }) => {
     // Get initial language from props, URL, localStorage, or default to 'en'
     const getInitialLanguage = () => {
         // Priority 1: Props
@@ -839,7 +844,7 @@ const AppHeader = ({ language: languageProp, accessToken: accessTokenProp }) =>
     React__default.useEffect(() => {
         const fetchProfilePicture = async () => {
             const token = accessTokenProp ?? getAccessTokenForRequest();
-            const blobUrl = await fetchProfilePictureAsBlobUrl(undefined, token ?? undefined);
+            const blobUrl = await fetchProfilePictureAsBlobUrl(objectStoreUrl ?? undefined, token ?? undefined);
             if (blobUrl) {
                 // Clean up previous blob URL if it exists
                 setProfilePictureBlobUrl((prevUrl) => {
@@ -860,7 +865,7 @@ const AppHeader = ({ language: languageProp, accessToken: accessTokenProp }) =>
                 return null;
             });
         };
-    }, [accessTokenProp]); // Refetch when accessToken prop changes (e.g. after login)
+    }, [accessTokenProp, objectStoreUrl]); // Refetch when accessToken or objectStoreUrl changes (e.g. after login or env switch)
     React__default.useEffect(() => {
         const allData = getAllDataFromStorage();
         let userName = "";