Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature/#146 keep content in sparql client #163

Merged
merged 18 commits into from
Apr 10, 2019

Conversation

AlexSerrano22
Copy link
Contributor

No description provided.

@MiguelAraCo MiguelAraCo changed the title Feature/#146 keep content in sparql client (WIP) Feature/#146 keep content in sparql client Nov 6, 2018
@AlexSerrano22 AlexSerrano22 changed the title (WIP) Feature/#146 keep content in sparql client Feature/#146 keep content in sparql client Nov 20, 2018
@AlexSerrano22
Copy link
Contributor Author

I did changes on this functionality to use Ngrx Stores to keep the sparql query on sparql client.

I did the implementation of state approach following this rules:

  • Create a folder named store in the main component.
  • Create actions and reducer folder with his files main-component.action or main-component.reducer.
  • If is necessary create a folder with the model of the object to store.
  • Create a ts file on the main component root folder, main-component.state to define the properties that this state could store. (maybe this point is the most important because we need define if we would follow this approach or define an unique state file).
  • Define on main-component.module imports StoreModule.forRoot({identifier: reducer import...}).

@mhernandeza mhernandeza merged commit cf99be9 into master Apr 10, 2019
@ghost ghost removed the in progress label Apr 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants