elmosoftware / my-recipes Goto Github PK

This need to be:

• Visible only for authenticated users.
• Need to be added as a menu item in the "Recetario" dropdown menu.
• Must display either all the recipes created by the user or a button followed by an encouraging message to create his first recipe.

We can't pretend that all the necessary ingredients for a user recipe are already there, right?.
So, we need to allow the user to add new ingredients right from the "RecipeComponent".

Secure the API using AUTH0 provider services for routes that need user authentication.

Right now, if you want to update a recipe step, you need to delete it and add it again.

We can only specify ascending order for sorting.

We need to apply some sort of progress indicator or spinning animation while the page is rendering or hitting the services.

Create the component we will need to add recipes to the site.
Also, we will need this to be linked from the "latest-recipes" component at the moment no recipes are in the repository.

• The following attributes can't be part of any JSON filters submitted by a client app:
  • "publishedOn"
  • "createdBy"
  • "lastUpdateBy"
• New query parameter "owner" with the following possible values:
  "me" -> Will retrieve all the entities of the requested kind owned by the user.
  "others" -> Will retrieve only entities owned by other users.
  "any" -> Will retrieve any entity regardless of which user is the owner.
• Change the "my-recipes" component to use this new query parameter instead of include user details in the JSON filter.

Evaluate to create a carousel component that can later been reuse for recipe images.

When the querystring variable "pop=true" is passed to the API, only the attributes to the parent document that are references to model entities are populated. If some of this entities include other entities, they are not populated.

We can fix this only up to first level subdocument entities.We can't go further because seems not to be supported in the current Mongoose version.

We need to implement the following server side security features.

For any Requests with GET method:

• Only Owners can request a Recipe or RecipeIngredient that is not published.
• Other not published entities can be requested only by ADMIN users.

For any Request with POST method:

• Anonymous users can't create an entity of any kind.
• Only ADMIN users can create entities other than Ingredient, Recipe and RecipeIngredient.

For any Request with PUT method:

• Anonymous users can't update any entity.
• Only the Owner can update Recipe and RecipeIngredients.
• Any other entity can be updated only by ADMIN users.

For any Request with DELETE method:

• Anonymous users can't delete any entity.
• Only the Owner can delete Recipe and RecipeIngredients.
• Any other entity can be deleted only by ADMIN users.

Steps to reproduce:

• Login as a social user.
• Type in the Browser directions text box the url "\user-preferences".

ER: You got a redirection to the "\error-unauthorized" page.
AR:You got the User preference page as not social users.

When we go for example to the /ingredients page, the ingredients are not sorted by name difficulting any task.

Final adjustments to have a clean move to prod env.

• Install GULP and configure GULP tasks.
• Prepare to deploy to [Now] (https://zeit.co/juancarlosgarcia).
• Clean orphan files and commented code.

Add the required to the recently added "recipe-view" component to display a recipe details.

The "Hoy quiero con..." panel in Home Page allows the user to search on Recipes containing specific ingredients.
We need to expand the current Search page functionality to take over this cases too.

Nav Bar is now in all pages but there is some functionality that must be only enable in Home page.

Make the necessary changes to publish an alpha version to the Production environment

Don't even think on show those real "carousel" images...
Replace them for a more appropriate pictures.
-We will use Cloudinary as CDN provider for holding Mis Recetas site images. For now we are talking about just the Carousel in home page but later we can add also user pictures on profiles, recipes, etc.
-We will add a /media endpoint in our API to act as a link with our CDN provider and retrieve the carousel images.

We need to be able to add a recipe :-)

Right now when you delete an entity is permanently deleted from the database.
The lack of referential integrity rules in the DB provider cause issues in the app when a document is missing.

The architectural approach to remediate this issue will be:

• Implement soft deletion through a field in the Entity model that indicates if the document is actually deleted.
• Implement a periodical batch job in the DB to find orphan documents and proceed to final deletion without to affect data consistency.

Must consider the following properties:

• Created on
• Created by
• Last update on
• Last updated by

Consider if needed some other workflow data, like: If the item must be published on the web site or since when, need to be evaluated.

Is not functional yet, let's do something about!

For now the Nav Bar created as part of the Home page. But we need to include it as part of any individual page. So we need to refactor it to expose that functionality through a new component.

This attribute, when set to "true", allows anyone to search and see the recipe.
If this attribute is set to "false", only the recipe owner can see it.

Implement Auth0 Authorization and Authentication service provide in the frontend.

The session keep opened only for not social users but only after a expensive back and forth with the Auth Service provider.

Right now we need t repeat code in every page that wants to use that functionality.

Right now each part of the app is in charge to invalidates the cache when needed. We need to automate most of this directly in the service.

when we go to a non existent page, the app is throwing an error instead of redirect to a 404 page.

Even when the user is not the owner, the "edit recipe" button still visible.

Apply same look and feel and apply "ngx-progressbar" too.

Evaluate the platform and make the required changes

When creating a new Ingredient in the new Recipe form, after saving the ingredient, is not showing in the list of ingredients even when the Ingredients cache get invalidated.

Let's start rising the expectations! :-)
Actually is to test the alias assigned to the APP.
Just a single page with a "coming soon" message also to test NOW static site deployments and alias settings.

That is a versy useful way to parse the response that need to e accessible to any part pf the app that need too deal with API services.

• All the Management API endpoints are protected.
• All the Data API enpoints are protected with the exception of GET method calls.

For those cases we need to implement the right request headers.

When filters includes character "/" part of the filter gets lost causing an exception in the API process.

Following topics to consider:

• When searching exact terms, (using quotes), there is no highlight in the results, (This is because the term is not between quotes in the results :-).
• Paginate searches in the following way: 1st search must retrieve a maximum of 5 results. A button must allow to search for next 10, and after that another button must be enable to retrieve all the pending results.

We need to show:

• Recipes created or updated recently.
• Add a "New" badge on the recipes recently created.

Every time you come back to Home page the recipes displayed in the "latest-recipes" component need to be loaded again. We need to:

• Add the 3 latest recipes to cache.
• Invalidate that cache every time a new recipes is added or deleted.

Unexpectedly start having issues debugging code with message "ENOENT: no such file or directory ...... /index.js/package.json'"

Solution: need to rename API folder :(

We can add new recipes but not edit an existing one.

Implement the Application cache, (Cache Class), in all other forms as required, (e.g.: Backend).

We need to show the 3 latest created recipes with basic information plus a link to view the recipe in full detail.

To reproduce the issue:
-1st - Create a new Recipes but do not publish it.
-2nd - Update the Recipe and publish it.

ER: The new recipe appears in the "Latest Recipes" section.
AR: The new recipe is not in the "Latest Recipes" section.

Add some content to the home page footer links.

When no recipe is already created the "crear una nueva" link is pointing to and old page that is not existing any more.