Skip to content
This repository has been archived by the owner on May 4, 2022. It is now read-only.

Define the uPortal context name (e.g. 'portal/' or 'uPortal/') in one place #758

Open
drewwills opened this issue Dec 15, 2017 · 2 comments

Comments

@drewwills
Copy link

I see a bunch of these...

          'SERVICE_LOC': {
            'aboutURL': '/portal/api/session.json',
            'sessionInfo': '/portal/api/session.json',
            'sidebarInfo': '/web/staticFeeds/sidebar.json',
            'newstuffInfo': '/web/staticFeeds/new-stuff.json',
            'context': '/portal/',
            'base': '/portal/api/',
            ...
@apetro
Copy link
Contributor

apetro commented Dec 18, 2017

Locally backlogged for MyUW Scrum purposes as MUMUP-3222.

@apetro apetro changed the title Please define the uPortal context name (e.g. 'portal/' or 'uPortal/') in one place Define the uPortal context name (e.g. 'portal/' or 'uPortal/') in one place Jan 9, 2018
@apetro
Copy link
Contributor

apetro commented Jan 9, 2018

Depending on how implemented, this is going to be an "API"-breaking change. Might be interesting to think through how to make this improvement in a backwards-compatible way so as to avoid forcing changes to adopter configuration on upgrade.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants