atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hemanth Yamijala (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ATLAS-318) UI. Config file containing UI: API endpoint + all api calls to be centralized -- config JS file for stand alone
Date Tue, 16 Feb 2016 06:02:18 GMT

    [ https://issues.apache.org/jira/browse/ATLAS-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15148136#comment-15148136
] 

Hemanth Yamijala commented on ATLAS-318:
----------------------------------------

Reviewed the latest patch. All review comments have been addressed. I am unable to reproduce
the problem with the caching - so it's fine. One thing is that the following two files still
have hardcoded URLs: app.js and definitionTagsController.js. I search for occurrences of /api/atlas
to find out what else is hardcoded. You could do this on your end before uploading the patch,
so that we will be good on that front. 

> UI. Config file containing UI: API endpoint + all api calls to be centralized -- config
JS file for stand alone
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: ATLAS-318
>                 URL: https://issues.apache.org/jira/browse/ATLAS-318
>             Project: Atlas
>          Issue Type: Task
>            Reporter: roshni gadiyar
>            Assignee: Darshan Kumar
>            Priority: Minor
>              Labels: Atlas-UI
>         Attachments: ATLAS-318-v1.patch, ATLAS-318.patch
>
>
> Config file conatining API endpoint + all api calls to be centralized -- config JS file
for stand alone UI.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message