jhipster / generator-jhipster-svelte Goto Github PK

No issues on Firefox

[INFO] npm ERR! code E404
[INFO] npm ERR! 404 Not Found - GET https://registry.npmjs.org/generator-jhipster-svelte - Not found
[INFO] npm ERR! 404
[INFO] npm ERR! 404 '[email protected]' is not in the npm registry.
[INFO] npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
[INFO] npm ERR! 404 It was specified as a dependency of 'test'

Svelte/Kit is still not publicly available (under development in a private repo). However, the bundle is available on npm. We really can't do MVP release with soon to be deprecated Sapper :(

Prerequisite issue #7

To verify user account activation and forgot password screens, need to identify a way to either access the email account or able to read the server console to retrieve activation key.

Probable candidates:

• Page layout
• Page Header
• Page Error
• Page Body

The current suite of unit tests merely test few components and are meant to verify jest integration and to satisfy build/sonar jobs. We should improve overall unit test coverage to cover all generated components

Related to #247

Current handling of authenticated route is not adequate as user can still access directly via browser. We should implement a solution similar to authorization to prevent unauthenticated users access to page contents.

• Create login page and integrate that with session based authentication.
• Update home page to redirect user post successful login and show authenticated user details

Currently like other frontend implementations, we use api/account to determine if the user has already been authenticated. Though the approach works and serves the purpose, it has a few unwanted side-effects:

• You can see 401 errors in your browser console and network requests and it doesn't look clean.
• Reduces lighthouse score

To mitigate the issue, we can replace the call with api/authenticate for authentication check purposes. In the case of authenticated users, it will return the authenticated user login name and for unauthenticated, an empty response.

It would be good to have night mode support. Initial support should be based on the tailwind class based approach.

• Upgrade JHipster dependency to use latest patch release
• Upgrade Svelte, Tailwind dependencies. Update tailwind configurations to remove build warning messages
• Upgrade other third-party dependencies

• Add new menu to restrict access to ADMIN role users
• It shall display a read only list of users available in the system
• It shall support pagination
• It shall support sort

• Adds ability to create a new user or update an existing user and integrate on the list page - #149
• Adds ability to view user details. - #143
• On list page:
  • Adds ability to activate/deactivate an existing user - #122
  • Adds ability to delete an existing user - #144

Post successful authentication, a user shall open the account activation link in the browser.

straight jhipster hands you a CURD based editor for each of your entities. jhipster-svelte should do the same.

@pascalgrimaud, Can you please help on:

• Create a repository with name - jhipster-sample-app-svelte
• Grant read/write access to @jhipster/svelte-admins team
• Link jhipster-sample-app-svelte on SonarQube

It's the second and final step in the password reset workflow, that can be accessed by a link in the password reset email.

After successful login, show account menu drop-down navbar options:

• Settings
• Change Password
• Logout

• To manage application dependencies, we need to externalize the package dependencies from .ejs templates.

Current execution of blueprint relies on globally installed generator-jhipster. With each new generator-jhipster release, it could cause compatibility issues. Further, a CLI can help to reduce the shipped docker image size

If you try to access any dynamically linked module, then, it fails with message like:

500
Failed to fetch dynamically imported module: http://localhost:8080/client/login.ef0c16ea.js
TypeError: Failed to fetch dynamically imported module: http://localhost:8080/client/login.ef0c16ea.js

No issues observed on Firefox

Workaround

Commenting out the service worker code fixes the issue

If an error occurs at server side, then, we need to parse the error contents and display appropriate error alerts on UI.

• Limit server side selection to Session based authentication and to monolithic applications
• Disable language selection prompts
• Remove protractor from test options

Related to jhipster/generator-jhipster#11935

Do you think is it possible @vishal423 ?
Do you want me to do it ?

Current generator code supports session authentication type. This issue is a placeholder to track integration with JWT authentication type

Add end to end tests to verify:

• Create user flow - Resolved by #238
• Update user flow - Resolved by #239
• View user details flow - Resolved by #237
• Delete user flow - Resolved by #236

Current generator code supports session authentication type. This issue is a placeholder to track integration with OIDC authentication type