Skip to content
This repository has been archived by the owner on Apr 11, 2023. It is now read-only.

feat: Auth vue setup and configure tailwind #37

Merged
merged 1 commit into from
Jul 23, 2020

Conversation

talwinder50
Copy link
Member

@talwinder50 talwinder50 commented Jul 23, 2020

closes #8

Signed-off-by: talwinder.kaur talwinder.kaur@securekey.com
Screen Shot 2020-07-22 at 3 58 55 PM

llorllale
llorllale previously approved these changes Jul 23, 2020
@codecov
Copy link

codecov bot commented Jul 23, 2020

Codecov Report

Merging #37 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master      #37   +/-   ##
=======================================
  Coverage   85.80%   85.80%           
=======================================
  Files           5        5           
  Lines         310      310           
=======================================
  Hits          266      266           
  Misses         29       29           
  Partials       15       15           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update eea0e67...dec7541. Read the comment docs.

# Copyright SecureKey Technologies Inc. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure if it's really important, but there's a "no newline" warning here showing up in the GitHub diff UI

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it shows up at the end of files.

It's actually good practice to always leave an empty line at the end of files. This way the diff is a bit less confusing if you happen to change the last line with contents

Comment on lines +17 to +22
src="https://upload.wikimedia.org/wikipedia/commons/thumb/5/53/Google_%22G%22_Logo.svg/512px-Google_%22G%22_Logo.svg.png"/>
Google
</a>
<a href="" class="mx-auto bg-gray-100 lg:mx-0 border hover:underline my-4 py-2 px-8 shadow-lg">
<img class="object-scale-down h-8 w-32" alt="Google &quot;G&quot; Logo"
src="https://upload.wikimedia.org/wikipedia/commons/9/91/Octicons-mark-github.svg"/>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a thought... Would it be a good idea if these resources are hosted internally? Just in case the external sitre goes down?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@talwinder50 WDYT?

Copy link
Member Author

@talwinder50 talwinder50 Jul 23, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I dont have very strong preference , Linking and embedding both have their pros and cons. Embedded images on git has to be stored on git lfs for the efficient storage purpose. If its not bothersome, i will set up git-lfs and add these images to the that in the following pr.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would probably vote for hosting it internally - I'm not sure if wikimedia ever moves their stuff around... but I think it would be fair to do it in a separate PR


module.exports = {
publicPath: "/ui"
}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Another no-newline warning

Copy link
Collaborator

@DRK3 DRK3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not familiar with Vue or JS, so it would probably be a good idea to have who is take a look as well

@llorllale llorllale dismissed their stale review July 23, 2020 20:32

UI is not being served

Copy link
Contributor

@llorllale llorllale left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@talwinder50 this UI is not being served by the backend

Copy link
Contributor

@baha-ai baha-ai left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The page looks good!

@llorllale
Copy link
Contributor

The page looks good!

Agreed - thanks @talwinder50 !

@llorllale
Copy link
Contributor

@talwinder50 this UI is not being served by the backend

@talwinder50 has agreed to do this in a followup PR

@talwinder50 talwinder50 force-pushed the issue-8 branch 2 times, most recently from d5b59a6 to fe7c6b3 Compare July 23, 2020 22:43
closes trustbloc#8

Signed-off-by: talwinder.kaur <talwinder.kaur@securekey.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Setup Vue project
4 participants